Public API Migration FAQ

Momentum AMP is upgrading its Public API to a newer version with updated endpoints and authentication options. Existing integrations will need to be migrated to the upgraded API.

The legacy Public API is scheduled for retirement on September 30, 2026.

The legacy API is scheduled to be retired on September 30, 2026. Clients should complete and test their migration before this date to avoid disruption. Any extension beyond the retirement date would need to be confirmed with Momentum AMP.

No. The migration applies to API integrations only. It does not affect your ability to log in to Momentum AMP, access your account, or access your existing client and payment information.

Your development team will need to update the integration to use the new API endpoints and supported authentication method. We recommend testing the changes in the staging environment before moving to production.

The endpoint changes are relatively minor for most integrations, but some endpoints and functionality have been updated or replaced. Your development team should review the migration guide and test the affected functionality.

Some legacy endpoints have been replaced or updated in the new API. The specific replacement depends on the functionality being used. Please refer to the migration guide for the current endpoint structure and available replacements.

Many of the existing API capabilities remain available, although some may use different endpoints or request/response structures. The migration guide and API documentation provide the current supported functionality.

The corresponding functionality should be handled through the appropriate endpoints in the new API. Please refer to the current API documentation for the replacement endpoints and required parameters.

Policy coverage information is available through the new API. The Policy Coverages endpoint can be used to retrieve coverage information using the applicable policy information.

These functions have been reviewed as part of the API transition. The applicable functionality should be implemented using the corresponding supported endpoints in the new API. Please refer to the migration documentation for the current endpoint details.

Availability varies by functionality. Some capabilities remain available through the new API, while others have been updated or replaced. The API documentation should be used to confirm the current endpoint and supported operations for each function.

These capabilities should be checked against the current API documentation because endpoint availability and implementation may differ from the legacy API.

The availability of individual legacy fields may differ in the new API. Please refer to the current endpoint response documentation to confirm whether a specific field is still supported.

The new API supports API-key authentication as well as the username/password token authentication flow.

API keys are not the only authentication option. The username/password authentication flow continues to be supported.

API keys can be generated from the Agency Profile under Actions → API Keys → Generate Key. API keys should be managed securely and can be revoked when necessary. Separate keys should be used for the applicable environments.

Yes. Staging and production use separate environments and credentials. A key generated for one environment should not be used in the other.

Production: https://api.momentumamp.com/
Staging: https://staging-api.momentumamp.com/

The new API supports a token-based authentication flow. A token is created through the token endpoint and can be refreshed using the refresh-token endpoint when required.

API access tokens expire after 24 hours. A refresh token can be used to obtain a new access token without repeating the full authentication process.

Development Support can provide access to a test agency and the appropriate staging credentials for migration testing.

Yes. Development Support can provide a test agency for clients who need to validate their integration before moving to production.

The API documentation and developer resources are available through the Momentum AMP developer portal at cip.momentumamp.com.

No. A Postman collection is not available for the new API. Developers should use the API documentation and staging environment for testing.

No. Existing webhooks are not affected by the Public API migration.

Zapier integrations using the legacy API may require migration to the new API. The migration should be coordinated and tested before the legacy API retirement.

The Public API migration and Momentum MCP are separate integrations. Clients using MCP should follow the applicable MCP documentation and guidance rather than treating the Public API migration as an MCP migration.

If a third-party integration uses the legacy Public API, the integration may need to be updated to use the new API before the legacy API is retired. Third-party integrations that do not use the affected API functionality may not require changes.

For technical questions or migration assistance, contact Momentum AMP Development Support or the appropriate integrations support team. Clients can also request staging access and test credentials through Development Support.