Skip to main content
If an app you use isn’t in the catalog but has a REST API, you can still connect it as a custom API. You describe the API once (its address, how it signs in, and which kinds of requests are allowed), and Crevio can call it for you. Your key is stored encrypted. It is never shown again, and Crevio’s AI never sees it: Crevio adds it to each request itself.

​
Add a custom API yourself

1

Open the form

Open Customize in the sidebar and choose the Connectors tab. Next to Add, open the menu and choose Add custom API.
2

Describe the API

  • Name: what you call it, for example “Acme CRM”.
  • Base URL: the address every request starts from, for example https://api.acme.com/v1. It must start with https:// and can’t include a ?query, a #fragment, or a username and password.
  • Allowed methods: tick GET, POST, PUT, PATCH or DELETE. Pick at least one. GET only reads; the others can change data in that app.
  • Authentication: Bearer token (paste the API token), API key in a header (enter the header name the API expects, such as X-Api-Key, and the key), API key in the URL (enter the query parameter the API expects, such as api_key, and the key), or No authentication.
  • Documentation URL (optional): a link to the API’s docs, which helps Crevio’s AI use it correctly.
3

Choose what Crevio may do

Select Add API. You land on its tools page, with one tool per method you allowed.

​
Decide what runs on its own

Each method is a tool with its own setting:
  • Run automatically: Crevio sends these requests without asking.
  • Ask for confirmation: Crevio shows you the request and waits for your approval each time.
  • Off: Crevio can’t send these requests.
GET starts on Run automatically and every other method starts on Ask for confirmation. Change any of them on the tools page, or later from the API’s tile on Connectors with Choose what Crevio may do.

​
Have Crevio set it up in chat

Ask in chat, for example “connect the Acme API, here are its docs”. Crevio reads the docs, sets the API up, and sends you a secure link titled Connect . Open it, sign in if asked, enter the key and select Save (for an API with no key, select Connect). The chat then carries on with what you asked for. Never paste a key into the chat: the link is the safe way, because what you type there goes straight to the connection and never into the conversation. The link works once and expires 24 hours after Crevio sends it. If it expired, ask Crevio for a new one.

​
Edit or remove it

Open the API’s tile on Connectors:
  • Edit API changes the name, base URL, methods or key. Leave the key empty to keep the stored one. If you change how it signs in, enter the new key too.
  • Choose what Crevio may do opens its settings page. The Access tab chooses who can use it: Whole team, Only me or Specific people, as for any other connection. The same page has the On switch and Locked.
  • Disconnect removes the API, its key and its tools. It can’t be undone.

​
Limits

  • Only APIs on the public internet over https://. Addresses on a private or internal network are refused.
  • Requests stay under the base URL: Crevio won’t send your key to any other address.
  • Sign-in methods are a bearer token, a key in a header, a key in the URL, or none. APIs that need OAuth sign-in or signed requests can’t be added this way. Check the catalog or ask Crevio for another route.
  • Members can add a custom API through chat only if an admin turned on Members can connect integrations in Settings → Team. The Connectors page itself is for admins.

​
Common problems

  • “Base URL must start with https://…”: copy the API’s base address, not a page of its website, and leave off anything after ?.
  • Requests come back with 401 or 403: the API rejected the key. Open Edit API and paste it again, or ask Crevio for a new link.
  • The link says it expired or was already used: ask Crevio for a new link.