Make your first API request

Medable API requests
To make your first Medable API request, you need to know four things:
1.The API endpoint: for example, api.<env>.medable.com/<org_code>
2.The API key: for example, mwidxhb8ShcqmV1B9iOYJh
3.Authentication credentials: an email and password
4.The API client: a terminal, web, iOS, or Android
The API endpoint
The endpoint for your API requests will look like the following:
HTTP
https://api.dev.medable.com/{{your_org_code}}/v2/{{api_resource}}
Where your_org_code is the org code you specified when signing up and api_resource is the resource you are trying to access, such as an account. And remember, since we're making this request to the development org, we use the api.dev.medable.com URL.
In our case, we'll use the example org code we used when we made the new app: newhealthco.
Note: When making requests, use the plural name for api_resource. For example, if the resource is account, use accounts in your endpoint: https://api.dev.medable.com/newhealthco/v2/accounts
The API key
Copy the API key that you generated in the previous step (see Generate an API key). In our example, the API key is mwidxhb8ShcqmV1B9iOYJh.
Authentication credentials
Because we specified that our app uses sessions, a username and password is needed to authenticate and initiate a user session.
For the username, use your email address. In our case, it's [email protected]. For the password, use the password you set when signing up.
If you're interested in signature-based authentication, see Authentication.
The API client
There are a number of tools out there that make it easy to make API requests. One option is Postman and another option is the live API explorer in the API Reference page. In this guide, we'll keep it simple and make our requests from the command line using curl.
Make a request
Note: This section is written assuming the request is being made through an OSX terminal.
Now that you're ready to make a request, you simply have to issue the command in the form of curl \[options...\] URL. Let's give it a shot using the API endpoint:
Request
Response
$ curl https://api.dev.medable.com/newhealthco/v2/accounts
{
    "object":"fault",
    "name":"error",
    "code":"kNotFound",
    "status":404,
    "reason":"Invalid application client api key.",
    "message":"Resource not found"
}
Tip: Add | python -m json.toolto the end of the curl request to pretty-print the JSON response.
We got a result back! Unfortunately, the result is a fault.
This is because we need to pass in a few more options to get the request to work. First, we need to add the API key header. We can do this using the following option:
-H "medable-client-key: mwidxhb8ShcqmV1B9iOYJh"
So let's give that a try:
Request
Response
$ curl -H "medable-client-key: mwidxhb8ShcqmV1B9iOYJh" https://api.dev.medable.com/newhealthco/v2/accounts
{
   "object":"list",
   "data":[
​
   ],
   "hasMore":false
}
The fault is gone, but now we get back an unexpected result. Rather than a list of accounts, which should at least have our own account in it, we get an empty result.
This is because the Account resource requires authentication to access. If we had tried to access a specific account using an account ID (575f58281d0c03a53ccc3ac6 in this case), we would receive a 403 error like so:
Request
Response
$ curl -H "medable-client-key: mwidxhb8ShcqmV1B9iOYJh" https://api.dev.medable.com/newhealthco/v2/accounts/575f58281d0c03a53ccc3ac6
{
   "object":"fault",
   "name":"error",
   "code":"kAccessDenied",
   "status":403,
   "reason":"Read access denied.",
   "message":"Access to this resource is denied"
}
So let's authenticate. To log in, we need to POST to the login route with our username and password. For more information on the Account resource and the available routes, see the API documentation on Accounts.
One more thing before we log in. For session-based apps, Medable uses cookies to track the session ID. So we need to enable cookie support in curl. To do this, we pass in the additional options:-b cookies.txt -c cookies.txt
The first option -b reads any existing cookies from cookies.txt and sends with the request. The second option -c writes any cookies coming from Medable to cookies.txt.
Request
Response
$ curl -b cookies.txt -c cookies.txt -H "medable-client-key: mwidxhb8ShcqmV1B9iOYJh" -d "email=jo[email protected]&password=This is not the password\!" https://api.dev.medable.com/newhealthco/v2/accounts/login
{
    "_id":"575f58281d0c03a53ccc3ac6",
    "object":"account",
    "created":"2016-06-14T01:04:40.888Z",
    "updated":"2016-06-14T01:08:06.647Z",
    "updater":{
       "_id":"575f58281d0c03a53ccc3ac6",
       "object":"account",
       "path":"/accounts/575f58281d0c03a53ccc3ac6"
    },
    "access":6,
    "favorite":false,
    "email":"[email protected]",
    "name":{
       "first":"John",
       "last":"Smith"
    },
    "mobile":"+15555555555",
    "locale":"en_US",
    "state":"verified",
    "locked":false,
    "key":{
       "fingerprint":"73ad85a0-31cc-11e6-ba07-3f24c7443557",
       "secret":"PXXvBvG86sJC2RVk4X6K4FV0OUH7ojzp"
    },
    "roles":[
       "000000000000000000000004",
       "000000000000000000000007",
       "000000000000000000000006"
    ],
    "shared":false
}
And we've successfully logged in! We know this because after a successful login, we receive our account object in the response.
If, instead of a response similar to the above, you receive a fault response that resembles this:
{
   "object": "fault",
   "name": "location",
   "code": "kNewLocation",
   "status": 403,
   "message": "A new location has been added to the account."
}
This means that two-factor authentication (2FA) has been initiated. Note that the fault could be kNewLocation, kUnverifiedLocation, or kLocationClientMismatch.
When this happens, you will receive a verification token via SMS to your mobile number. Once you receive that token, you'll need to authenticate again as well as send along verificationToken like so:
curl -b cookies.txt -c cookies.txt -H "medable-client-key: mwidxhb8ShcqmV1B9iOYJh" -d '[email protected]&password=NotYourPassword&location[verificationToken]=123456' https://api.medable.com/newhealthco/v2/accounts/login
For more information on 2FA, see Two-factor authentication.
Now that we've logged in and have an active session, let's try that account request again.
Request
Response
$ curl -b cookies.txt -c cookies.txt -H
"medable-client-key: mwidxhb8ShcqmV1B9iOYJh"
-d "email=jo[email protected]&password=This is not the password\!"
https://api.dev.medable.com/newhealthco/v2/accounts/login
{
    "_id":"575f58281d0c03a53ccc3ac6",
    "object":"account",
    "created":"2016-06-14T01:04:40.888Z",
    "updated":"2016-06-14T01:08:06.647Z",
    "updater":{
       "_id":"575f58281d0c03a53ccc3ac6",
       "object":"account",
       "path":"/accounts/575f58281d0c03a53ccc3ac6"
    },
    "access":6,
    "favorite":false,
    "email":"[email protected]",
    "name":{
       "first":"John",
       "last":"Smith"
    },
    "mobile":"+15555555555",
    "locale":"en_US",
    "state":"verified",
    "locked":false,
    "key":{
       "fingerprint":"73ad85a0-31cc-11e6-ba07-3f24c7443557",
       "secret":"PXXvBvG86sJC2RVk4X6K4FV0OUH7ojzp"
    },
    "roles":[
       "000000000000000000000004",
       "000000000000000000000007",
       "000000000000000000000006"
    ],
    "shared":false
}
Success! You've made your first API request!
Generate an API key
Configure the org settings
Last modified 2yr ago