Atlas CRM Cloud
  • Atlas CRM Cloud
  • Release notes 2025
  • Release notes 2024
  • Release notes 2023
  • Release notes 2022
    • November 21st
    • September 8th
    • June 14th
    • June 1st
    • May 19th
    • May 11th
    • March 31st
    • March 15th
    • March 9th
    • March 2nd
    • February 21st
    • February 16th
    • February 4th
    • February 2nd
    • January 22nd - Atlas CRM 2.0
    • January 13th
    • January 10th
  • Getting started
    • Checklist
    • Core concepts
    • Installation
    • Language settings
    • Pricing
  • User functionalities
    • Companies
    • Contacts
    • Sales
    • Jira issues
    • Interactions
      • Manual Interactions
      • Gmail Integration
        • Installation
        • Feature overview
        • Admin settings
      • Outlook Integration
        • Installation
        • Feature overview
        • Admin settings
      • Jira Service Management Requests
    • Custom JQL
      • Practical examples
      • Queues in Jira Service Management
      • Gadgets on dashboards
      • Custom JQL automations
    • Confluence pages
    • Export
    • User preferences
  • Gmail integration
  • Admin configuration
    • Templates
    • Import
    • Sales configuration
    • Atlas CRM data on Jira issues
    • Access and User roles
      • Granting access to Atlas CRM
      • Customising User roles
    • Automations
      • Triggers
        • Issue created
        • Issue comment added
        • Issue updated
        • Contact linked to issue
        • Company linked to issue
        • Sale linked to issue
      • Actions
        • Link company based on custom field
        • Link contact based on custom field
        • Link contact based on reporter's email
        • Link company based on reporter's email
        • Copy template fields to custom fields
        • Link a linked company
        • Link a linked contact
        • Log issue as interaction
      • Configure an automation
        • Select trigger and actions
        • Publishing your automation
        • Disabling an automation
    • User synchronization
    • JSM Connect
    • API
      • Authentication
      • Endpoints
  • Privacy / Security
    • Security policy
  • Relevant links
  • Marketplace
  • Support
  • Roadmap
  • Server / Data Center documentation
Powered by GitBook
On this page
  • Fetch with request header
  • Fetch with request body

Was this helpful?

  1. Admin configuration
  2. API

Authentication

Authenticate with the Atlas CRM API

In order to work with the API you will need an access token. You can obtain an access token by creating a client secret and client id through the API tokens UI in the Atlas CRM settings.

You can find the API tokens by navigating to settings in the top right corner of the app and then selecting the dropdown item API tokens.

Note: API tokens will always get admin privileges

After creating a new API token you will be presented with 2 fields: client secret and client id . You will need both to fetch an access token with the following command:

Fetch with request header

You will need to base64 encode your "YOURCLIENTID:YOURCLIENTSECRET" and perform a POST request to the token endpoint using basic authentication.

curl "https://atlascrm.avisi-apps.com/api/1.0/oauth/token" \
    -H "Authorization: Basic BASE64ENCODED" \
    -H "Content-Type: application/x-www-form-urlencoded" \
    -d "grant_type=client_credentials"

Notice that the grant_type should be specified inside the body of the request. If you are not using curl make sure to also set the Content-Type header to application/x-www-form-urlencoded .

Fetch with request body

You can also make a POST request using only the body. If you are not using curl make sure to also set the Content-Type header to application/x-www-form-urlencoded .

curl "https://atlascrm.avisi-apps.com/api/1.0/oauth/token" \ 
    -H "Content-Type: application/x-www-form-urlencoded" \
    -d "grant_type=client_credentials" \
    -d "client_id=YOURCLIENTID" \
    -d "client_secret=YOURCLIENTSECRET"

This token is valid for 1 hour and you will need to fetch a new bearer token with your client secret and client id to get a new one.

You can now query our API with the authorization header "Bearer YOUR_ACCESS_TOKEN".

Last updated 9 months ago

Was this helpful?