personal access token for API calls to DevRev
ART-1175_KNOWLEDGE_NODE-4
a DevRev API must include a PAT. After you create your account, [generate a personal access token](/about/authentication) and store it in a safe place.\n\nIn this guide, you\xe2\x80\x99ll make a call to the [`dev-users.self`](/api-reference/dev-users/self) API which gets the authenticated user\xe2\x80\x99s information. You will retrieve the user object created for your account on DevRev. This user object contains information such as a unique identifier, full name, display name, and profile
Getting started | DevRev | Docs
ART-1371_KNOWLEDGE_NODE-4
must include a PAT. After you create your account, [generate a personal access token](/public/about/authentication) and store it in a safe place.\n\nIn this guide, you\xe2\x80\x99ll make a call to the [`dev-users.self`](/public/api-reference/dev-users/self) API which gets the authenticated user\xe2\x80\x99s information. You will retrieve the user object created for your account on DevRev. This user object contains information such as a unique identifier, full name, display name, and profile
Getting started — DevRev | Docs
ART-1362_KNOWLEDGE_NODE-4
customer). The application uses its own AAT to authenticate to the STS to obtain a session token for a customer and then uses that session token to access DevRev APIs. The lifetime of a session token is usually minutes. The subject of the session token is set to the DON of the corresponding customer (for example, `don:identity:dvrv-us-1:devo/0:revo/6:revu/131`).\n\n  * **Personal Access Token (PAT)** : Uniquely identifies a dev user. A PAT can be used by external applications to access DevRev
Authentication — DevRev | Docs
ART-1362_KNOWLEDGE_NODE-7
token is valid at [jwt.io](https://jwt.io/).\n\n## Generate a personal access token (PAT)\n\n  1. In the DevRev app, go to the relevant dev org.\n  2. Go to **Settings** > **Account** > **Personal Access Token**.\n  3. Click **New token** and follow the workflow to create your PAT.\n\n#####\n\nAs the token value isn\xe2\x80\x99t retrievable later, using descriptive names for PATs is recommended as it can help you differentiate between multiple PATs.\n\n  \n\n  1. Copy the PAT and store it
Authentication — DevRev | Docs
ART-1170_KNOWLEDGE_NODE-5
DevRev APIs on behalf of the corresponding dev user. The lifetime of a PAT is usually in days. The subject of the PAT is set to the corresponding dev users DON (for example, `don:identity:dvrv-us-1:devo/0:devu/30`).\n\nPersonal access token usage\n---------------------------\n\nAuthentication to DevRev APIs requires a personal access token (PAT). A PAT is used to uniquely identify a dev user in context of a dev org and can be used by external third-party applications to access DevRev APIs on
Authentication | DevRev | Docs
ART-1312_KNOWLEDGE_NODE-0
b'\xf0\x9f\x91\x89 Getting started\nIf you are new to DevRev, we would recommend learning about our core concepts before getting started.\nOnce you have a DevRev account, you can access the APIs with a personal access token (PAT) that you create in the DevRev app.\nA brief tutorial shows you how to access the APIs.\n\xf0\x9f\xa7\xac Methods\nSpecifications covering the supported APIs are based on OpenAPI Specification 3.0. You can download the specs to use an OpenAPI 3.0-compliant tool to
For Developers – DevRev | Docs
ART-1362_KNOWLEDGE_NODE-5
APIs on behalf of the corresponding dev user. The lifetime of a PAT is usually in days. The subject of the PAT is set to the corresponding dev users DON (for example, `don:identity:dvrv-us-1:devo/0:devu/30`).\n\n## Personal access token usage\n\nAuthentication to DevRev APIs requires a personal access token (PAT). A PAT is used to uniquely identify a dev user in context of a dev org and can be used by external third-party applications to access DevRev APIs on behalf of the corresponding dev
Authentication — DevRev | Docs
ART-1170_KNOWLEDGE_NODE-4
customer (or customer). The application uses its own AAT to authenticate to the STS to obtain a session token for a customer and then uses that session token to access DevRev APIs. The lifetime of a session token is usually minutes. The subject of the session token is set to the DON of the corresponding customer (for example, `don:identity:dvrv-us-1:devo/0:revo/6:revu/131`).\n* **Personal Access Token (PAT)**: Uniquely identifies a dev user. A PAT can be used by external applications to access
Authentication | DevRev | Docs
ART-1371_KNOWLEDGE_NODE-3
find your newly created org in **Orgs**.\n\nLogin into your demo org and [obtain the PAT token](/public/about/authentication#generate-a-personal-access-token-pat). Now you can use this PAT token to make test API calls and try building something new.\n\nIn this tutorial, you will be able to retrive your account information by using the `dev-users` API. Let\xe2\x80\x99s get started with DevRev APIs.\n\n## Prerequisites\n\nFirst, create a DevRev account or log in.\n\nEvery call to a DevRev API
Getting started — DevRev | Docs
ART-1366_KNOWLEDGE_NODE-2
Developers\n\n## \xf0\x9f\x91\x89 Getting started\n\nIf you are new to DevRev, we would recommend learning about our [core concepts](https://docs.devrev.ai/intro) before getting started.\n\nOnce you have a DevRev account, you can access the APIs with a [personal access token](/public/about/authentication) (PAT) that you create in the DevRev app.\n\nA brief [tutorial](/public/api-reference/getting-started) shows you how to access the APIs.\n\n## \xf0\x9f\xa7\xac Methods\n\nSpecifications
For Developers — DevRev | Docs
ART-1299_KNOWLEDGE_NODE-0
b'Beta\nOn this page\n\n\xf0\x9f\x91\x89 Getting started \xf0\x9f\xa7\xac Methods \xf0\x9f\xa7\xa9 Snap-ins \xf0\x9f\x92\xbb SDKs\n\nAbout For Developers.\n\n\xf0\x9f\x91\x89 Getting started.\n\nIf you are new to DevRev, we would recommend learning about our core concepts before getting started.\n\nOnce you have a DevRev account, you can access the APIs with a personal access token (PAT) that you create in the DevRev app.\n\nA brief tutorial shows you how to access the APIs.\n\n\xf0\x9f\xa7\xac
For Developers — DevRev | Docs
ART-1170_KNOWLEDGE_NODE-7
error, you can check whether the token is valid at [jwt.io](https://jwt.io/).\n\nGenerate a personal access token (PAT)\n--------------------------------------\n\n1. In the DevRev app, go to the relevant dev org.\n2. Go to **Settings** > **Account** > **Personal Access Token**.\n3. Click **New token** and follow the workflow to create your PAT.\n\n![]()\n\n##### \n\nAs the token value isn\xe2\x80\x99t retrievable later, using descriptive names for PATs is recommended as it can help you
Authentication | DevRev | Docs
ART-1175_KNOWLEDGE_NODE-3
can find your newly created org in **Orgs**.\n\nLogin into your demo org and [obtain the PAT token](/about/authentication#generate-a-personal-access-token-pat).\nNow you can use this PAT token to make test API calls and try building something new.\n\nIn this tutorial, you will be able to retrive your account information by using the `dev-users` API. Let\xe2\x80\x99s get started\xc2\xa0with DevRev APIs.\n\nPrerequisites\n-------------\n\nFirst, create a DevRev account or log in.\n\nEvery call to
Getting started | DevRev | Docs
ART-1353_KNOWLEDGE_NODE-1
[Mobile](/about/for-developers#mobile)\n\n[About](/about/for-developers)\n\nFor Developers\n==============\n\nCopy page\n\n\xf0\x9f\x91\x89 Getting started\n-----------------\n\nIf you are new to DevRev, we would recommend learning about our [core concepts](https://docs.devrev.ai/intro) before getting started.\n\nOnce you have a DevRev account, you can access the APIs with a [personal access token](/about/authentication) (PAT) that you create in the DevRev app.\n\nA brief
For Developers | DevRev | Docs
ART-16579_KNOWLEDGE_NODE-12
replace the `<AAT>` and `<YOUR_USER_ID>` with the actual values.\n\n```\n|  |  |\n| --- | --- |\n| $ | curl \\ |\n| > | --location \'https://api.devrev.ai/auth-tokens.create\' \\ |\n| > | --header \'accept: application/json, text/plain, */*\' \\ |\n| > | --header \'content-type: application/json\' \\ |\n| > | --header \'authorization: <AAT>\' \\ |\n| > | --data \'{ |\n| > | "rev_info": { |\n| > | "user_ref": "<YOUR_USER_ID>" |\n| > | } |\n| > | }\' |\n```\n\nThe response of the API call
Features | DevRev | Docs
ART-1371_KNOWLEDGE_NODE-6
issues.\n\nNext, you\xe2\x80\x99ll want to set up your development environment to connect and interact with the DevRev API.\n\n## Send your first API request\n\nTo do this, make a GET request to the DevRev server (\xe2\x80\x9c<https://api.devrev.ai/dev-users.self>[](https://api.devrev.ai/dev-users.self)\xe2\x80\x9d) and include the PAT created in the authorization header of the request.\n\nThis guide shows you how to get user information with a GET request using two popular languages as well as
Getting started — DevRev | Docs
ART-1175_KNOWLEDGE_NODE-6
issues.\n\n![]()\n\nNext, you\xe2\x80\x99ll want to set up your development environment to connect and interact with the DevRev API.\n\nSend your first API request\n---------------------------\n\nTo do this, make a GET request to the DevRev server (\xe2\x80\x9c<https://api.devrev.ai/dev-users.self>\xe2\x80\x9d) and include the PAT created in the authorization header of the request.\n\nThis guide shows you how to get user information with a GET request using two popular languages as well as
Getting started | DevRev | Docs
ART-1170_KNOWLEDGE_NODE-6
behalf of the corresponding dev user. A PAT has the same set of privileges that the owner of the PAT has on the DevRev platform.\nYou can set the validity duration of a PAT. You can\xe2\x80\x99t renew a PAT; you can only create a new PAT and update your code to use it.\nFor example, a VS Code plugin that pulls issues from the DevRev platform pertaining to a particular dev user needs to rely on that user\xe2\x80\x99s PAT to authenticate the DevRev APIs.\nIf you are receiving an `invalid token`
Authentication | DevRev | Docs
ART-1362_KNOWLEDGE_NODE-6
user. A PAT has the same set of privileges that the owner of the PAT has on the DevRev platform. You can set the validity duration of a PAT. You can\xe2\x80\x99t renew a PAT; you can only create a new PAT and update your code to use it. For example, a VS Code plugin that pulls issues from the DevRev platform pertaining to a particular dev user needs to rely on that user\xe2\x80\x99s PAT to authenticate the DevRev APIs. If you are receiving an `invalid token` error, you can check whether the
Authentication — DevRev | Docs
ART-1170_KNOWLEDGE_NODE-8
differentiate between multiple PATs.\n\n  \n\n1. Copy the PAT and store it securely. Once you go to another page, you can\xe2\x80\x99t retrieve this PAT again.\n\nRevoke a personal access token\n------------------------------\n\n##### \n\nOnce a PAT is revoked, it can\xe2\x80\x99t be restored. Never share tokens with other users or applications. Do not publish tokens in public code repositories.\n\n1. In the DevRev app, go to the relevant dev org.\n2. Go to **Settings** > **Account** >
Authentication | DevRev | Docs
ART-16803_KNOWLEDGE_NODE-29
**Account**](https://app.devrev.ai/?setting=account) and create a **New token** under **Personal Access Tokens**. Add the token here to create a new connection.\n3. Enter the **URL endpoint** where you want to send or fetch data. The URL can be static or dynamically built using reference outputs from previous steps.\n4. Select the **HTTP request method**: GET, POST, PUT, or DELETE.\n5. Configure the **authentication type** for the request.\n6. Add any required **headers**. Headers carry
Workflow nodes | Workflows | Computer by DevRev | DevRev
ART-1175_KNOWLEDGE_NODE-7
cURL:\n\n### Making a GET request\n\ncURLPythonNode JS\n\n```\n|  |  |\n| --- | --- |\n| $ | curl --location --request GET \'https://api.devrev.ai/dev-users.self\' \\ |\n| > | --header \'Authorization: Bearer <PAT>\' |\n```\n\nIf everything works, the command line displays the following response for a user named \xe2\x80\x9cJohn Smith Doe\xe2\x80\x9d:\n\nResponse\n\n```\n|  |  |\n| --- | --- |\n| 1 | { |\n| 2 | "dev_user": { |\n| 3 | "display_handle": "John Doe", |\n| 4 | "created_date":
Getting started | DevRev | Docs
ART-2046_KNOWLEDGE_NODE-27
update the app by navigating to **Apps** > **Manage apps** > **DevRev for Jira**. DevRev will notify administrators of major updates.\n\nConfiguration\n-------------\n\nTo configure the app go to **Apps** > **Manage Apps** > **DevRev for Jira**.\n\n![]()\n\n1. Go to the DevRev app and retrieve the platform access token by clicking **Settings** > **Account** > **New token**.\n2. Copy both the token and its corresponding token name. Paste them into the appropriate input fields within the app
DevRev for Jira app | Jira Software AirSync | AirSync | Snap-ins | DevRev