Summary and recommendation
Proposify's public API authenticates via OAuth 2.0 Bearer tokens, with the authorization code flow handled at auth.proposify.com. The API is scoped primarily to proposal and document lifecycle operations - no dedicated user-management or team-management endpoints are publicly documented as of early 2025.
OAuth scopes are not publicly enumerated in the developer documentation; required scopes must be confirmed directly with Proposify. Rate limit details are similarly undocumented, making capacity planning for any integration speculative without direct vendor engagement.
For teams building identity graph pipelines or access review automation, Proposify's API surface is a significant constraint. There is no programmatic path to create, update, or deactivate users today.
API quick reference
| Has user API | No |
| Auth method | OAuth 2.0 (Bearer token) |
| Base URL | Official docs |
| SCIM available | No |
| SCIM plan required | Business |
Authentication
Auth method: OAuth 2.0 (Bearer token)
Setup steps
- Register an application in the Proposify developer portal to obtain a client_id and client_secret.
- Direct users through the OAuth 2.0 authorization code flow at https://auth.proposify.com/oauth/authorize.
- Exchange the authorization code for an access token at https://auth.proposify.com/oauth/token.
- Include the access token as a Bearer token in the Authorization header of all API requests.
User object / data model
User object field mapping is not yet verified for this app.
Core endpoints
Endpoint coverage is not yet verified for this app.
Rate limits, pagination, and events
Rate limits: Rate limit details are not publicly documented by Proposify.
Rate-limit headers: Unknown
Retry-After header: Unknown
Rate-limit notes: No official rate limit documentation found. Contact Proposify support for current limits.
Pagination method: none
Default page size: Not documented
Max page size: Not documented
Pagination pointer: Not documented
Webhooks available: Yes
Webhook notes: Proposify supports webhooks for proposal lifecycle events (e.g., viewed, signed, closed). User-management-specific webhook events are not documented.
Alternative event strategy: Poll the proposals API for status changes if webhook delivery is unreliable.
Webhook events: proposal.viewed, proposal.signed, proposal.closed, proposal.sent
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Business
- Endpoint: Not documented
Limitations:
- SCIM user provisioning is listed as 'coming soon' in Proposify's official documentation as of early 2025.
- SSO is available on the Business plan via OIDC with Okta, Azure AD, and Salesforce, but automated user provisioning/deprovisioning via SCIM is not yet supported.
- Azure AD integration uses OIDC, not SAML.
Common scenarios
The only automation-ready scenario currently supported is proposal lifecycle monitoring via webhooks. Proposify supports events including proposal.
viewed, proposal. signed, proposal.
sent, and proposal. closed, registered through Settings → Integrations → Webhooks and consumed as POST payloads at a caller-supplied endpoint.
No user-management webhook events such as user. created or user.
deactivated are available, which means Proposify cannot participate in event-driven identity graph updates without a polling layer.
SSO configuration on the Business plan is an admin UI operation, not an API operation. OIDC is supported with Okta, Azure AD, and Salesforce; Azure AD specifically requires OIDC and does not support SAML, a common misconfiguration risk for teams defaulting to SAML-first IdP setups.
User invitation and deactivation have no API equivalent. Both actions require manual execution in the Proposify web UI at Settings → Team.
Invite a user to Proposify workspace
- No public API endpoint for user invitation or creation is documented.
- Users must be invited manually via the Proposify web UI (Settings > Team Members > Invite).
- Monitor for SCIM availability announcements to automate this workflow in the future.
Watch out for: There is no programmatic user-creation endpoint available as of early 2025.
Enable SSO for team members
- Upgrade to the Business plan.
- Navigate to Settings > Security in the Proposify admin panel.
- Configure OIDC with your identity provider (Okta, Azure AD, or Salesforce).
- Distribute the SSO login URL to team members.
Watch out for: Azure AD integration uses OIDC only, not SAML. Ensure your IdP configuration matches OIDC requirements.
Monitor proposal activity via webhooks
- Authenticate via OAuth 2.0 to obtain an access token.
- Register a webhook endpoint URL in Proposify Settings > Integrations > Webhooks.
- Select events such as proposal.signed or proposal.viewed.
- Handle incoming POST payloads at your registered endpoint.
Watch out for: Webhook events cover proposal lifecycle only; no user-management events (e.g., user.created, user.deactivated) are available.
Why building this yourself is a trap
The primary integration trap is building any automated provisioning or deprovisioning workflow against Proposify's current API surface. SCIM is listed as coming soon in official documentation but carries no committed release date; any workflow built in anticipation of that endpoint will require rework once the spec is published.
OAuth scope requirements are undocumented, meaning token requests may fail or return insufficient permissions without prior coordination with Proposify support. This makes Proposify a poor candidate for unattended service-account integrations until the developer documentation matures.
For identity graph completeness, Proposify user state must currently be sourced by scraping the Settings → Team UI or via manual export - there is no API-based roster endpoint to sync against. Teams relying on automated access reviews should flag Proposify as a manually-managed application until SCIM ships.
Automate Proposify workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
