• Creating, updating, or retrieving a developer configuration
• Accessing anonymized bulk data
• Accessing utility data

Generate a Token

1. Retrieve your client_id and client_secret from the Developer Dashboard.
2. With the client_id and client_secret, you can make a POST call to the Authorization Server with your credentials to exchange them for a JWT:
Copy

curl --request POST \
  --url https://dev-jhhgu9vc.auth0.com/oauth/token \
  --header 'content-type: application/json' \
  --data '{"client_id":"{YOUR_CLIENT_ID}","client_secret":"{YOUR_CLIENT_SECRET}","audience":"https://link-money-api/","grant_type":"client_credentials"}'

If the Authorization Server recognizes your client_id and client_secret, it will respond with a JSON payload containing the JWT:

Copy

{
	"token": "{YOUR_BEARER_TOKEN}",
	"type": "Bearer"
} 

3. Use the token value to make your calls to resources requiring a generic token by including it as a Bearer token in your Authorization header.
Copy

curl --request GET \
  --url https://link-money-api-development.herokuapp.com/plaid/v1/transactions/get/v1/generic_resource \
  --header 'Authorization: Bearer {YOUR_BEARER_TOKEN}'

Considerations

• Generic tokens target only developer resources, not user resources.
• Generic tokens should not be user-facing and should be for internal use only.
• Generic bearer tokens in Link Money remain valid for one hour before they expire.

Generate a User-Specific JWT.

1. Retrieve your client_id and client_secret from the Developer Dashboard.
2. Retrieve the ID of the user for the token. Depending on your developer configuration, this value could be user.uid, user.id, or user.guid.
3. Make a call to the Authorization server with your Oauth2 credentials and the valid user ID in the payload. For this example, we will use guid as the ID field, though any of the three are considered valid:
Copy

curl --request POST \
  --url https://dev-jhhgu9vc.auth0.com/oauth/token \
  --header 'content-type: application/json' \
  --data '{"client_id":"{YOUR_CLIENT_ID}","client_secret":"{YOUR_CLIENT_SECRET}","guid":{USER_ID}", "audience":"https://link-money-api/","grant_type":"client_credentials"}'

4. If the Authorization server recognizes your Oauth2 credentials, it will respond with a JSON payload containing the user-specific bearer token:
Copy

{
	"token": "{YOUR_BEARER_TOKEN}",
	"type": "Bearer"
} 

5. Call to a user-specific resource in FindMoney with this bearer token to retrieve data for the specified user:
Copy

curl --request GET \
  --url https://linkmoney.fingoal.com/v1/{user-specific-resource} \
  --header 'Authorization: Bearer {YOUR_BEARER_TOKEN}'

Considerations

• User tokens access only resources that are user-specific.
• User tokens expire after 3 hours, after which point they must be regenerated.
• User tokens will be generated regardless of whether the user with the specified ID exists in the LinkMoney API. Calls to user-specific endpoints with tokens that are for a non-existent user will return {} empty JSON.

Create an Item-Specific JWT

1. Retrieve your client_id and client_secret from the Developer Dashboard.
2. Retrieve the item_id for the item you want to authenticate (See Link Money Gateway Calls)
3. Retrieve the organization for the organization you want to authenticate with.
4. Make a call to the authorization server with your Oauth2 client credentials and the item_id in the payload:
Copy

curl --request POST \
  --url https://dev-jhhgu9vc.auth0.com/oauth/token \
  --header 'content-type: application/json' \
  --data '{"client_id":"{YOUR_CLIENT_ID}","client_secret":"{YOUR_CLIENT_SECRET}","item_id":{YOUR_ITEM_ID},"audience":"https://link-money-api/","grant_type":"client_credentials", "organization": {YOUR_ORG_ID}}'

5. If the Authorization server recognizes your Oauth2 credentials, it will respond with a JSON payload containing the item-specific bearer token:
Copy

{
	"token": "{YOUR_BEARER_TOKEN}",
	"type": "Bearer"
} 

6. Call to an item-specific resource in Link Money with this bearer token to retrieve data for the specified user:
Copy

curl --request GET \
  --url https://linkmoney.fingoal.com/v1/plaid/item-specific-resource \
  --header 'Authorization: Bearer {YOUR_BEARER_TOKEN}'

Considerations

• Item tokens access only resources that are item-specific.
• Item tokens expire after 24 hours, after which point they must be regenerated.
• Item tokens will be generated regardless of whether the item with the specified ID exists in the Link Money API. Calls to item-specific endpoints with tokens that are for a non-existent item will return {} empty JSON.

Create a Generic Token

1. Retrieve your client_id and client_secret from the Developer Dashboard.
2. Concatenate these values into a single string separated by a colon: my_client_id:my_client_secret.
3. Base64 encode the value. In this example, the encoded value is bXlfY2xpZW50X2lkOm15X2NsaWVudF9zZWNyZXQ=.
4. Prepend Basic to the value to create the header:

Basic bXlfY2xpZW50X2lkOm15X2NsaWVudF9zZWNyZXQ=

5. In your HTTP call, use this as the Authorization header:
Copy

curl -H "Authorization: Basic bXlfY2xpZW50X2lkOm15X2NsaWVudF9zZWNyZXQ=" https://linkmoney.fingoal.com/v1/mx

Create a Specific (User) Token

1. Retrieve your client_id and client_secret from the Developer Dashboard.
2. Retrieve the guid of the user.
3. Concatenate these values into a single string seperated by colons:

my_client_id:my_client_secret:user_guid

4. Base64 encode the value. In this example, the encoded value is

bXlfY2xpZW50X2lkOm15X2NsaWVudF9zZWNyZXQ6dXNlcl9ndWlk

5. Prepend Basic to the value to create the header:

Basic bXlfY2xpZW50X2lkOm15X2NsaWVudF9zZWNyZXQ6dXNlcl9ndWlk

6. In your HTTP call, use this as the Authorization header:
Copy

 curl -H "Authorization: Basic bXlfY2xpZW50X2lkOm15X2NsaWVudF9zZWNyZXQ6dXNlcl9ndWlk" https://linkmoney.fingoal.com/v1/mx/user-specific-resource

• 200 OK
• 201 Created
• 202 Accepted
• 203 Non-Authoritative Information
• 204 No Content