Summary and recommendation
No publicly documented user-management or SCIM API endpoints exist for Returnly as of this research. The standalone Returnly developer portal (developers.returnly.com) may be deprecated or redirected following the 2021 Affirm acquisition.
Any previously issued Returnly API credentials or integrations may require migration to Affirm's platform - verify current credential validity with Affirm before building any automation.
The Affirm developer portal (developers.affirm.com) does not currently expose user-provisioning endpoints for the Returnly product surface.
API quick reference
| Has user API | No |
| SCIM available | No |
Authentication
Auth method: Not documented
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: Not documented
Rate-limit headers: No
Retry-After header: No
Rate-limit notes: Not documented
Pagination method: none
Default page size: 0
Max page size: 0
Pagination pointer: Not documented
Webhooks available: No
Webhook notes: No publicly documented webhook events for user-management found in official Returnly or Affirm documentation.
Alternative event strategy: Not documented
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: Not documented
- Endpoint: Not documented
Limitations:
- No publicly documented SCIM support found for Returnly.
- Returnly was acquired by Affirm in 2021; enterprise identity features are not publicly documented.
- Contact Affirm enterprise sales for current SSO/SCIM availability.
Common scenarios
No automatable user-management scenarios can be documented at this time. There are no confirmed endpoints for user creation, deactivation, role assignment, or seat enumeration in either the Returnly or Affirm public API references.
If Affirm introduces a user-management API in a future release, the expected integration patterns would include identity graph traversal to correlate Returnly merchant accounts with upstream IdP identities - but this cannot be implemented against current documented APIs.
Teams requiring automation should escalate to Affirm enterprise sales and request API roadmap details under NDA if necessary.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The primary integration trap here is assuming the pre-acquisition Returnly API surface is still valid. Returnly was absorbed into Affirm's merchant platform, and any API keys, base URLs, or webhook configurations from the standalone era are of unknown status.
There is no documented auth method, no confirmed rate-limit behavior, no pagination contract, and no SCIM endpoint - attempting to build identity graph synchronization against undocumented or potentially deprecated endpoints will produce silent failures or broken deprovisioning flows.
Without a confirmed, versioned API contract from Affirm, any automation built on assumptions carries high maintenance risk and should not be used in production access-control workflows.
Automate Returnly 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.
