Get access

Use the Resia portal to manage your organization, your teammates, and your API keys. An API key lets your software act for your organization. It does not sign you in to the portal.

Join the right organization

Every person belongs to exactly one organization. If your team already uses Resia, ask a teammate for an invitation before you create a new organization.

Open the invitation link

Use the link from your invitation email.

Sign in with the invited email address

Sign in with Google, GitHub, or an emailed sign-in link. Use the email address on the invitation.

Accept the invitation

You now have the same access as every other member. Resia has no separate roles.

If you are the first person on a new account, sign in and create your organization in the portal. A new organization starts with $10.00 of free credit. The home page then shows the setup steps for a new organization.

The portal home page for a new organization, with a box to describe a call and the five setup steps

To add teammates, open Settings → Members and select Invite member.

The Members tab in portal settings, with two members and the Invite member button

Already have a key, but cannot see your account? A key does not create a personal membership. Ask your Resia contact to connect your login to the organization, or email support@resia.ai with your account email and organization name. Never send your API key.

Create an API key

Open API Keys

In the portal, open Settings → API Keys.

The API Keys tab in portal settings, with two active credentials and the Create credential button
Create a credential

Select Create credential and enter a name that identifies the software that will use the key, such as billing-service-prod. Choose the key's scope: Reader reads, Editor also creates, changes, and starts work, and Owner also deletes. Give the key the lowest scope that its software needs. See What an API key can do.

The Create credential dialog with a Name field
Store the key

Copy the complete key to your secret store before you close the dialog. Resia shows the secret once. If you lose it, create a new key.

To rotate a key, create the new key, update your software, and then revoke the old key. Revocation takes effect immediately and cannot be undone. To change a key's scope, rotate the key in the same way.

An API key cannot create other keys, invite people, or remove members. Those actions need a person who is signed in to the portal. See Authentication.

Prepare your terminal

The guides use a Bash terminal with curl, jq, and uuidgen installed:

  • curl sends HTTPS requests.
  • jq reads and builds JSON.
  • uuidgen creates a unique key for each request that must not run twice.

If your terminal uses another shell, such as zsh on macOS, run bash first. In zsh, the read -p command below fails and leaves the key empty, so the test request returns 401.

Set your base URL and your key once. The read -s command keeps the key out of your shell history.

export RESIA_API_BASE='https://api.resia.ai'
read -r -s -p 'Resia API key: ' RESIA_API_KEY
printf '\n'
export RESIA_API_KEY

Test the key:

curl --fail-with-body --silent --show-error \
  "$RESIA_API_BASE/v1/call-agents?limit=1" \
  --header "Authorization: Bearer $RESIA_API_KEY"

Expected result: HTTP 200 and a JSON object with an items list. An empty list is fine.

If it fails: HTTP 401 means Resia did not accept the key. Check that you copied the complete key and that nobody revoked it.

Keep this terminal open. The other guides reuse RESIA_API_BASE and RESIA_API_KEY.

Next step