Shape is a powerful and flexible platform that can operate as a standalone system or connect seamlessly with external tools and applications. Through OpenAPI, HTTP posts, Zapier, and webhooks, Shape allows you to build advanced integrations and automate data flow across your tech stack.

What the Shape OpenAPI Supports

Shape’s OpenAPI provides public-facing endpoints that allow approved systems to interact directly with your CRM. Once enabled, these endpoints can be used to create, update, search, and manage records programmatically.

Common OpenAPI use cases include:

  • Creating new leads
  • Updating record data
  • Changing statuses and assignments
  • Searching for existing records
  • Bulk importing and exporting data

The update record endpoint is especially powerful, allowing you to update multiple fields, reassign users, and change status in a single API call.

Enabling and Accessing the OpenAPI

To use the OpenAPI, it must be enabled within your Shape settings. Each request requires two key values to authenticate and route the request correctly.

Required OpenAPI credentials:

  • Authorization API key
  • CRM ID

Both values are found under Settings → API Integrations, and the API key must be copied in full for requests to succeed.

Field Mappings and JSON Formatting

Shape’s OpenAPI uses JSON formatting for all requests. Field mappings determine which data points can be retrieved or updated and can be found throughout the platform, most commonly within marketing sources.

Field mappings are used to:

  • Update contact data
  • Change statuses
  • Assign users or departments
  • Retrieve record information

Status updates must match the exact status value and status list as it appears in the system.

Updating Records Using the OpenAPI

When updating a record, the lead ID is required. This ID can be found directly in the contact record URL or retrieved using the search endpoint.

With a single API call, you can:

  • Update source information
  • Add or modify contact fields
  • Change record status
  • Reassign users or departments

Successful updates return the lead ID as confirmation. A response of zero indicates an error in the request.

Using HTTP Posts for Lead Creation

In addition to OpenAPI, Shape supports HTTP POST methods for lead creation. This method is commonly used with marketing tools like Facebook Lead Ads.

Key differences between OpenAPI and HTTP POST:

  • OpenAPI supports full record management
  • HTTP POST supports lead creation only
  • HTTP POST supports form or JSON data
  • OpenAPI requires JSON formatting only

HTTP POST requests do not require authorization keys but do require specific fields such as first name, last name, email, and source.

Combining Zapier, Webhooks, and OpenAPI

Zapier and webhooks can be used along side the OpenAPI to build multi-step workflows. A common approach is creating a lead via HTTP POST, then updating or assigning the record using OpenAPI calls.

These workflows can:

  • Create records
  • Search for newly created leads
  • Update contact fields
  • Assign users or departments
  • Trigger automation like drip campaigns

Lead IDs returned from one step can be passed into subsequent steps to complete advanced automation chains.

Why This Video Matters

Integrations are critical for scaling your workflows and eliminating manual data entry. Shape’s OpenAPI gives you precise control over how data enters, updates, and moves through your system, while still triggering the automations and processes you rely on. Whether you’re syncing marketing leads, updating records in real time, or building advanced workflows with Zapier, the OpenAPI ensures Shape fits seamlessly into your existing ecosystem.