Nylas Applications API

In the context of the Nylas APIs, an "application" is the object record of your Nylas application. 🔍 The term "application" can refer to any of three concepts: your Nylas application, the project you're building ("your application" or "your app"), and applications that you use to connect to service providers ("provider auth applications"). We try to be specific in this documentation to avoid confusion. The API endpoints described here are for working with your Nylas application, specifically. The Nylas application is the central resource for your Nylas implementation. It collects the [connectors](/docs/reference/api/connectors-integrations/) that you use to store information about third party services that your application connects to, and stores the [grants](/docs/reference/api/manage-grants/) that you create when using connectors. Nylas applications also allow you to define your specific branding, change the look and feel of the Nylas Hosted authentication flow, and list your application's callback URIs. ## Application callback URIs Your Nylas application includes a list of allowed callback URIs. These are known URIs that Nylas can direct users to after authentication. You need to define at least _one_ callback URI so your users can complete the auth flow. You must include any callback URIs you plan to use in this list. If an auth payload includes a callback URI that isn't on the list, the whole authentication flow fails. ## Application limitations ⚠️ You can create, edit, and delete applications from the Nylas Dashboard. You cannot create, edit, or delete them using the Nylas APIs. Keep the following limitations in mind as you work with Nylas applications: - Applications are the central resource that stores other Nylas resources. You _must_ create an application before you can create any other parts of your Nylas implementation. - Applications can be associated with only one project at a time. While your project can have more than one Nylas application to provide different authentication experiences, you cannot share applications, connectors, or grants between more than one project. - Applications cannot be nested, and cannot be set up with parent-child relationships. - Your application must have _at least one_ callback URI, or else it cannot finish the authentication flow, which means it cannot create grants. Nylas requires grants to access user data. - In an ideal scenario, your application will have multiple callback URIs defined.

Business capability
Developer Identity & Credential Management BC-4270.40

Operations 7

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /v3/applications View my Nylas application settings · Get application #
Ask an LLM
“How can I see the region, environment and branding of my application?”
“Where do I find my Nylas application's configuration details?”
Tell an agent
Show my application's settings.
Get the application object for this API key.
PATCH /v3/applications Update application branding and hosted auth · Update an application #
Ask an LLM
“Can I change the branding shown on my application's hosted authentication page?”
“How do I update my application's hosted authentication settings through the API?”
Tell an agent
Update my application's branding to {branding}.
Set the hosted authentication settings for my app to {hosted_authentication}.
GET /v3/applications/redirect-uris List my application's callback URIs · Get an application's callback URIs #
Ask an LLM
“Which redirect URIs are registered on my application?”
“How do I see all the callback URLs users can return to after auth?”
Tell an agent
List every callback URI on my application.
Show all registered redirect URIs.
POST /v3/applications/redirect-uris Register a new callback URI · Add callback URI to application #
Ask an LLM
“How do I add a redirect URI so users return to my app after authenticating?”
“What platform is used if I don't specify one for a new callback URI?”
Tell an agent
Add a new callback URI to my application.
Register another redirect URI for the web platform.
GET /v3/applications/redirect-uris/{id} Retrieve one callback URI · Return a callback URI #
Ask an LLM
“Can I look up a single callback URI by its ID?”
“What settings are stored on a specific redirect URI?”
Tell an agent
Get callback URI {id}.
Show the details of redirect URI {id}.
PATCH /v3/applications/redirect-uris/{id} Change an existing callback URI · Update a callback URI #
Ask an LLM
“Can I edit the URL or platform of a callback URI I already registered?”
“Does updating a redirect URI keep its platform if I leave it out?”
Tell an agent
Update callback URI {id}.
Edit the settings on redirect URI {id}.
DELETE /v3/applications/redirect-uris/{id} Remove a callback URI · Delete a callback URI #
Ask an LLM
“How do I delete a redirect URI I no longer use?”
“Can I remove an old callback URL from my application?”
Tell an agent destructive · confirm first
Delete callback URI {id}.
Remove redirect URI {id} from my application.

Documentation

Specifications

Schemas & Data

Other Resources

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/nylas:nylas-applications-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

nylas-applications-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Nylas Applications API
  version: v3
  summary: The complete Nylas v3 API — Email, Calendar, Contacts, Notetaker, Scheduling, Administration, and Migration.
  description: The Nylas API is designed using the REST ideology to provide simple and predictable URIs to access and modify objects. Requests support standard HTTP methods like `GET`, `PUT`, `POST`, and `DELETE`, and standard status codes. Response bodies are always UTF-8 encoded JSON objects, unless explicitly documented otherwise. You can use the Nylas Postman collection to quickly start using the Nylas APIs. For more information, check out the Nylas Postman collection documentation.
  contact:
    url: https://www.nylas.com/
servers:
- url: https://api.us.nylas.com
  description: U.S.
- url: https://api.eu.nylas.com
  description: E.U.
security:
- ACCESS_TOKEN: []
- NYLAS_API_KEY: []
tags:


# --- truncated at 32 KB (43 KB total) ---
# Full source: https://artifacts.apis.io/nylas/openapi/nylas-applications-api-openapi.yml