How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Integration.app (Membrane)

Integration.app (Membrane) Field Mappings API

The Field Mappings API from Integration.app (Membrane) — 2 operation(s) for field mappings.

Documentation Provider Profile APIs.io OpenAPI GitHub

Integration.app (Membrane) Field Mappings API is one of 43 APIs that Integration.app (Membrane) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Field Mappings. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 14 operations across 10 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.getmembrane.com.

14 operations 10 paths 13 schemas 1 DELETE5 GET1 PATCH6 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.getmembrane.com
Authentication
HTTP Bearer, HTTP Bearer
Contact
Membrane Documentation
Resource Areas
1

Authentication & Security 2

Integration.app (Membrane) Field Mappings API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It accepts HTTP bearer tokens (JWT) (bearer). By default, every request must be authenticated.

  • bearerAuth — Bearer token in the Authorization header. Test tokens are available from workspace settings; admin-level tokens are required for administrative operations.

Paths & Operations 14

Across 10 paths, the API surfaces 14 operations — 1 DELETE, 5 GET, 1 PATCH, 6 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Field Mappings 14
GET
/field-mappings
List field mappings
listFieldMappings → 200
POST
/field-mappings
Create field mapping
createFieldMapping body → 201
GET
/field-mappings/{selector}
Get field mapping
getFieldMapping 1 param → 200
PATCH
/field-mappings/{selector}
Update field mapping partially
patchFieldMapping 8 params body → 200
PUT
/field-mappings/{selector}
Replace field mapping completely
replaceFieldMapping 8 params body → 200
DELETE
/field-mappings/{selector}
Archive field mapping
archiveFieldMapping 8 params → 200
GET
/field-mappings/{selector}/app-schema
Get field mapping app schema
getFieldMappingAppSchema 7 params → 200
POST
/field-mappings/{selector}/clone
Clone field mapping
cloneFieldMapping 7 params → 200
GET
/field-mappings/{selector}/dependencies
Get dependencies of field mapping (flat interface)
getFieldMappingDependencies 7 params → 200
GET
/field-mappings/{selector}/export
Export field mapping (flat interface)
exportFieldMapping 7 params → 200
POST
/field-mappings/{selector}/refresh
Refresh field mapping
refreshFieldMapping 7 params → 200
POST
/field-mappings/{selector}/reset
Reset field mapping
resetFieldMapping 7 params → 200
POST
/field-mappings/{selector}/restore
Restore field mapping (flat interface)
restoreFieldMapping 7 params → 200
POST
/field-mappings/{selector}/run
Run a field mapping
runFieldMapping 7 params body → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are FieldMappingApiResponse (53 properties), UpdateFieldMapping (31 properties), CreateFieldMapping (31 properties), UpdateFieldMapping__schema0 (28 properties). Each schema is shown below with its type and property counts.

FieldMapping
object
5 properties
FieldMappingApiResponse__schema1
object
28 properties
CreateFieldMapping
object
31 properties
FieldMappingExportProperties__schema0
object
28 properties
FieldMappingApiResponse
object
53 properties 2 required
FieldMappingExportProperties
object
23 properties 2 required
CreateFieldMapping__schema0
object
28 properties
UpdateFieldMapping__schema0
object
28 properties
FieldMappingAppSchemaResponseDto
object
RunFieldMappingResponseDto
object
1 property
FieldMappingApiResponse__schema0
object
7 properties 1 required
RunFieldMappingRequestDto
object
3 properties
UpdateFieldMapping
object
31 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

integration-app-field-mappings-api-openapi.yml Raw ↑

Other APIs Integration.app (Membrane) publishes across the network.

Integration.app (Membrane) Actions API
AE Profile APIs.io
Integration.app (Membrane) App Event Subscriptions API
AE Profile APIs.io
Integration.app (Membrane) Connections API
AE Profile APIs.io
Integration.app (Membrane) Connectors API
AE Profile APIs.io
Integration.app (Membrane) Customers API
AE Profile APIs.io
Integration.app (Membrane) Data Collections API
AE Profile APIs.io
Integration.app (Membrane) External Event Subscriptions API
AE Profile APIs.io
Integration.app (Membrane) Flow Runs API
AE Profile APIs.io
Integration.app (Membrane) Flows API
AE Profile APIs.io
Integration.app (Membrane) Integrations API
AE Profile APIs.io
Integration.app (Membrane) Logs API
AE Profile APIs.io
Integration.app (Membrane) Public API
AE Profile APIs.io
#Field Mappings
← Back to I APIs
API Details
ID
integration-app:integration-app-field-mappings-api
Base URL
https://api.getmembrane.com
Docs
https://getmembrane.com
Provider
Integration.app (Membrane)
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=integration-app-field-mappings-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/integration-app-field-mappings-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Integration.app (Membrane) Field Mappings API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.