Build on Pitch2Sale with personal access tokens for your own scripts, and OAuth apps for tools that act on a user's behalf. Every request runs with that user's permissions, so the API never sees more than they could.
Your script sends a token with each request. Pitch2Sale checks the token's scopes and its user's role, then answers with only what that user may see.
Twelve read and write scopes across leads, contacts, opportunities, invoices, proposals and projects.
A token carries its user's role, so it never sees more than they would.
OAuth 2.0 with PKCE and refresh tokens, and a consent screen for the user.
See when each token was last used and revoke it instantly.
Admins can create tokens and apps by default.
Give the token a Label.
All scopes start ticked.
It is shown once.
Enter the app name, an optional description and redirect URIs, one per line, then pick scopes and click Create.
Send the token as Authorization: Bearer …. The developer docs list every endpoint.
| Direction | What | When |
|---|---|---|
| Your tool → Pitch2Sale | Reads and writes on leads, contacts, opportunities, invoices and proposals, within the token's scopes | Each request |
| Pitch2Sale → your tool | JSON responses limited to what the token's user can see | Each request |
| Pitch2Sale → your tool | OAuth access tokens (one hour) and refresh tokens | When a user approves your app |
| Not synced | Nothing is pushed by the API itself; use outbound webhooks for events | — |
Personal access tokens last until you revoke them. OAuth access tokens last an hour and refresh.
It is shown only once. Revoke it and create a new one.
Yes, 300 requests a minute from one address.
Yes, with outbound webhooks.
Create a scoped token in Settings and make your first call in minutes.