Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

You can access the token via authentication in API using username and password. (edited) 

 

cURL Request to authenticate:
curl -X POST -d user[email]="user@example.com" -d user[password]="pwd" https://staging.makerble.com/api/v2/users/sign_in
Response:
{"user_id": 1, "email": "user@example.com", "authentication_token": "<long token>"}

cURL request to access api
curl --header "X-User-Token: <long token>" --header "X-User-Email: user@example.com" https://staging.makerble.com/api/v2/beneficiary_categories

Related information

  • If you want activity to be recorded about multiple users (as though they were individual users on the web platform) you should build API interactions with every user rather than only having API interactions go via an Organisation Admin user.

  • However if the integration that you are building does not require that actions be attributed to specific users, you could instead only build API interactions with a single Organisation Admin user

  • There is no expiry of each authentication token. Each user has a fixed token.

  • No labels