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

Flipdish MetafieldDefinitions API

Operations for Metafield Definitions.

Flipdish MetafieldDefinitions API is one of 85 APIs that Flipdish publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 6 operations across 4 paths, and defines 10 schemas. It is described by OpenAPI 3.0.3, at version v1.0.

Requests are made against a single base URL, https://api.flipdish.co.

6 operations 4 paths 10 schemas 4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
v1.0
Base URL
https://api.flipdish.co
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Flipdish MetafieldDefinitions API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the implicit and clientCredentials flows, exposing 1 scope. By default, every request must be authenticated.

  • oauth2 — OAuth 2.0. Implicit grant for first-party portal apps; client credentials grant for server-to-server App Store apps (exchange Client ID + Secret Key for a bear…

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 4 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

MetafieldDefinitions 6

Operations for Metafield Definitions.

GET
/api/v1.0/{appId}/metafields/definitions
Flipdish Get Owner Entity Configurations
GetOwnerEntityConfigurations 1 param → 200400401403500
GET
/api/v1.0/{appId}/metafields/definitions/{ownerEntity}/{key}
Flipdish Get Metafield Definition by Key
GetMetafieldDefinitionByKey 3 params → 200400401403500
POST
/api/v1.0/{appId}/metafields/definitions/{ownerEntity}/{key}
Flipdish Update Metafield Definition
UpdateMetafieldDefinition 3 params body → 200400401403500
GET
/api/v1.0/{appId}/metafields/definitions/{ownerEntity}
Flipdish Get Metafield Definitions
GetMetafieldDefinitions 5 params → 200400401403500
POST
/api/v1.0/{appId}/metafields/definitions/{ownerEntity}
Flipdish Create Metafield Definition
CreateMetafieldDefinition 2 params body → 200400401403500
GET
/api/v1.0/{appId}/metafields/definitions/recommendations/{ownerEntity}
Flipdish Get Owner Entity Recommendations
GetOwnerEntityRecommendations 5 params → 200400401403500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are CreateMetafieldDefinition (8 properties), MetafieldDefinition (8 properties), MetafieldDefinitionRecommendation (7 properties), RestApiPaginationResult_MetafieldDefinition_ (4 properties). Each schema is shown below with its type and property counts.

MetafieldDefinitionRecommendation
object
OwnerEntity Metafield Definition Recommendation
7 properties 2 required
CreateMetafieldDefinition
object
Information to create a {Flipdish.Metafields.PublicModels.V1.MetafieldDefinition}
8 properties 2 required
RestApiPaginationResult_MetafieldDefinition_
object
Rest api pagination result
4 properties 4 required
RestApiPaginationResult_MetafieldDefinitionRecommendation_
object
Rest api pagination result
4 properties 4 required
RestApiResult_MetafieldDefinition_
object
Rest api result
1 property 1 required
FlipdishError
object
Standard Flipdish API error response. Errors are returned as a JSON object with a human-readable message and a programmatic error code (see https://developers.…
1 property
MetafieldDefinition
object
Metafield Definition
8 properties 2 required
OwnerEntityConfigurations
object
Owner Entity Configurations
1 property
OwnerEntityConfiguration
object
OwnerEntity information to configure its {Flipdish.Metafields.PublicModels.V1.MetafieldDefinition}s
2 properties
UpdateMetafieldDefinition
object
Information to update a {Flipdish.Metafields.PublicModels.V1.MetafieldDefinition}
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flipdish-metafielddefinitions-api-openapi.yml Raw ↑

Other APIs Flipdish publishes across the network.

Flipdish Accounts API
Flipdish Address API
Flipdish Apm API
Flipdish Apps API
Flipdish AppStore API
Flipdish AppStoreConfigurations API
Flipdish AppStoreDeveloper API
Flipdish AppStoreEntitlements API
Flipdish AuditLogs API
Flipdish AuthorizationTokens API
Flipdish BankAccount API
Flipdish Campaigns API
Where this information came from

This is an independent, third-party profile of Flipdish MetafieldDefinitions 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.