Using the Momentum AMS REST API

Base URL

All API requests are made to:

https://api.nowcerts.com

API method documentation is available here:
Momentum AMS API Help Page

Authentication

Before making requests, you must obtain an access token.
The account you use must have the Agent role “API Integration” assigned.

Token Request URL:

https://api.nowcerts.com/token

Required Parameters (x-www-form-urlencoded):

• username → Your Momentum AMS username

• password → Your Momentum AMS password

• grant_type → password (hardcoded)

• client_id → ngAuthApp (hardcoded)

Example POST request:

POST /token Content-Type: application/x-www-form-urlencoded 
username=YOUR_USERNAME &password=YOUR_PASSWORD &grant_type=password &client_id=ngAuthApp

Response:
A JSON object containing your access_token, which you must include in the Authorization header for all requests:

Authorization: Bearer {access_token}

Working with Common API Methods

Insureds

• Required fields: Either:

  • CommercialName (creates a Commercial insured), OR

  • FirstName & LastName (creates a Personal insured)

• Examples:

  • POST api/Insureds → Import an insured

  • GET api/Insureds → Retrieve insureds list

• Sample project: InsuredsRestApi.aspx on GitHub

Policies

• Example methods:

  • POST api/Policies → Import a policy

  • GET api/Policies → Retrieve policy data

• Sample project: PoliciesRestApi.aspx on GitHub

Prospects

• Example method:
  POST api/Zapier/InsertProspect
  (Despite “Zapier” in the route, this is a standard API method.)

Logic to prevent duplicate prospects:

1. If database_id is given → search by ID

2. If not found → search by email address

3. If not found → search by first & last name

4. If not found → search by commercial name

5. If found → overwrite attributes (address, phone, etc.)

6. If still not found → create a new prospect

Zapier & Automation Methods

While labeled as “Zapier,” these can be used by any application:

• GET api/Zapier/GetInsureds → Retrieve insured data

• POST api/Zapier/InsertInsured → Insert insured data

Search Methods

• Simple search:

  • Name, address, email, phone

• Complex search:

  • Filter, paging, sorting

• Example POST endpoint:

  POST api/Customers/GetCustomersList
  

Advanced Feature – Importing One Insured with Multiple Policies

A newer API method allows you to send one request that creates:

• An insured record

• Multiple policies linked to that insured

(Check the API help page for the expected object format.)

Developer Resources

We maintain a public GitHub repository with code samples:

• AuthenticateRestApi.aspx – Authentication example

• InsuredsRestApi.aspx – Insured import

• PoliciesRestApi.aspx – Policy import

Best Practices

• Always test with a non-production account first.

• Use descriptive names for form or automation sources so you can trace imported records later.

• Store the access_token securely and refresh it before it expires.

• Validate data before sending to avoid overwriting key insured or policy details.