How to set up API access to Content Snare
Content Snare uses OAuth 2.0 for its API, so instead of a single secret key you register an "application" in your account and Content Snare gives you a client id and client secret. A connected tool uses those to ask you to authorise it, and once you approve, it can read your requests, clients, templates, and the files and answers your clients have submitted, all through the API rather than by logging in as you. Access is scoped to the role and permissions of the person who authorises the connection, and you can change the application or remove its access at any time without affecting your normal login. This guide walks through registering the application, finding the client id and client secret, choosing scopes, and revoking access when it is no longer needed.
Keep this credential safe
A client id and client secret are like a password. Anyone who has the client secret, together with an authorised connection, can access whatever the granted scopes allow. Scope the application to read-only access where the tool does not need to make changes, share the client id and secret only through a secure method such as a password-manager share link rather than plaintext email or chat, and delete or rotate the application as soon as the connection is no longer needed.
Access to grant
An OAuth 2.0 application (client id and client secret) registered in your account, scoped to the smallest set of API scopes the connecting tool needs.
Who you're granting access to
- The developer, consultant, or tool that will read your data through the Content Snare API.
Before you start
- An Admin role in your Content Snare account. Only Admins can view Settings and modify integrations, webhooks, and connected apps.
- The redirect URL from the developer or tool that will connect, so the OAuth flow can return to their app after you authorise it.
- A secure way to share the client id and client secret with that developer or tool (a password-manager share link, not plaintext email or chat).
Step by step
- 1
Open Settings, then the API integration
Sign in to Content Snare as an Admin. Click your avatar in the top right and select Settings. Under Integrations, select API. If you do not see this option, you are not on an Admin role and will need someone with Admin access to do this step.
- 2
Create a new application
On the API page, click Create a New Application. This registers an OAuth 2.0 application in your account that a tool can connect to. You can create more than one application if different tools need their own credentials.
- 3
Enter the name, description, and redirect URL
Enter a Name and Description so you can recognise the application later (for example, the name of the tool or developer connecting). Enter the Redirect URL, which is the address the developer or tool gives you for where Content Snare should send the OAuth response after you authorise it. The redirect URL must match exactly, so copy it rather than typing it.
- 4
Choose the smallest set of scopes
Select only the scopes the connecting tool actually needs. Content Snare recommends choosing the smallest subset of scopes that the application requires, so if the tool only needs to read data, do not grant scopes that allow changes. Narrow scopes limit what anyone with the credential can do.
- 5
Copy the client id and client secret, then share them securely
Once the application is saved, Content Snare shows the client id and client secret on the application screen. Treat the client secret like a password. Copy both values and pass them to the developer or tool through a secure method such as a password-manager share link, never plaintext email or a chat message. When the tool runs the OAuth flow, you (or whoever authorises it) sign in and approve, and access is granted at that person's role and permission level.
Removing access afterwards
- Click your avatar in the top right and select Settings.
- Under Integrations, select API.
- Find the application in your list of applications.
- Delete the application (or rotate it by deleting and creating a fresh one with a new client secret). Removing the application stops any tool using its credentials from reaching the API.
If that option is not available
If you would rather not register an application yourself, an Admin can screen-share on a short call and create it together while the developer reads out the redirect URL and notes down the client id and secret securely. You should never need to share your Content Snare password. If the connection only needs to push data into Content Snare on a one-off basis, ask whether a no-code connector (for example, Make or Zapier) can do it under its own managed authorisation instead.
Frequently Asked Questions
Content Snare uses OAuth 2.0, so you register an application that has a client id and a client secret rather than one standalone API key. A tool uses those credentials to ask you to authorise it, and Content Snare then issues the access it needs through the OAuth flow.
Treat the client secret like a password. Copy it once when the application is created, store it in a password manager, and share it with the developer or tool through a secure password-manager share link rather than plaintext email or chat. If you ever suspect the secret has been exposed, delete the application and create a new one so the old credentials stop working.
A connected application can reach the parts of the API allowed by the scopes you select and the role of the person who authorises the connection. That can include your requests, clients, templates, and the files and answers your clients have submitted. Choosing the smallest set of scopes keeps that access tight.
Go to Settings, then under Integrations select API, find the application, and delete it. Deleting it stops any tool using its credentials from reaching the API. To rotate, delete the application and create a fresh one, then update the connecting tool with the new client id and client secret.
You need the Admin role. Content Snare only lets Admins modify integrations, webhooks, and connected apps, so Viewer, Reviewer, and Editor roles will not see the API option under Settings.
The redirect URL is the address Content Snare sends the OAuth response to after you authorise the application. The developer or tool that is connecting provides it. It must match exactly, so copy and paste it into the application form rather than typing it by hand.
Related guides
Steps last checked against Content Snare on 2026-06-09.
Based on official Content Snare documentation: Content Snare help centre: Getting started with the API, Content Snare partner API documentation, Content Snare help centre: Team and permissions. Content Snare is a trademark of its respective owner; this guide is independent and for instruction only.
Want this handled for you?
Clever Ops connects and automates the systems mid-market businesses already run. Book a free assessment and we will map your stack.