Fluid Company APIs (1.0)

The Fluid Company APIs provide a comprehensive set of APIs designed to integrate Fluid's powerful services into your applications seamlessly. These APIs use Company API tokens for authentication and provide full access to manage your company's resources including users, orders, products, media, and more.

For APIs that authenticate with User tokens, see the Rep APIs documentation.

Download OpenAPI description
Overview
E-mail support@fluid.app
License MIT
Languages
Servers
Mock server
https://docs.fluid.app/_mock/docs/apis/company.api/
Production server with company subdomain
https://{company}.fluid.app/
Local development server
http://fluid.lvh.me:{port}/

Activities

Operations

Admins

Operations

Agreements

Operations

Announcements

Operations

ApplePay

Operations

Application Theme Resources

Operations

Application Theme Templates

Operations

Application Themes

Operations

Authentication

Operations

Bank Accounts

Operations

Brand Guidelines

Operations

Business Types

Operations

Callback Definitions

Operations

Callback Registrations

Operations

Callback Schemas

Operations

Carts

Operations

Catch Ups

Operations

List custom catch ups

Request

curl -i -X GET \
  https://docs.fluid.app/_mock/docs/apis/company.api/api/company/custom_catch_ups \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Responses

successful

Bodyapplication/json
catch_upsArray of objects
metaobject
Response
application/json
{ "catch_ups": [ {} ], "meta": { "request_id": "string", "timestamp": "string" } }

Create custom catch up

Request

Bodyapplication/json
affiliate_idintegerrequired

ID of the UserCompany record for the affiliate creating the catch-up

titlestringrequired
descriptionstring
typestringrequired

Type identifier for the catch-up

contact_idinteger
actionsobject

Structured actions data

curl -i -X POST \
  https://docs.fluid.app/_mock/docs/apis/company.api/api/company/custom_catch_ups \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "affiliate_id": 0,
    "title": "string",
    "description": "string",
    "type": "string",
    "contact_id": 0,
    "actions": {}
  }'

Responses

successful

Bodyapplication/json
catch_upobject
metaobject
Response
application/json
{ "catch_up": { "id": 0, "company_id": 0, "user_company_id": 0, "suggestion_title": "string", "suggestion_description": "string", "catch_up_class": "string", "catch_up_actions": [], "created_at": "string", "updated_at": "string" }, "meta": { "request_id": "string", "timestamp": "2019-08-24T14:15:22Z" } }

Update custom catch up

Request

Path
idstringrequired

CatchUp ID

Bodyapplication/json
suggestion_titlestring
suggestion_descriptionstring
curl -i -X PATCH \
  'https://docs.fluid.app/_mock/docs/apis/company.api/api/company/custom_catch_ups/{id}' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "suggestion_title": "string",
    "suggestion_description": "string"
  }'

Responses

successful

Bodyapplication/json
catch_upobject
metaobject
Response
application/json
{ "catch_up": { "id": 0, "company_id": 0, "user_company_id": 0, "suggestion_title": "string", "suggestion_description": "string", "catch_up_class": "CUSTOM_CATCH_UP", "catch_up_actions": [], "created_at": "string", "updated_at": "string" }, "meta": { "request_id": "string", "timestamp": "string" } }

Delete custom catch up

Request

Path
idstringrequired

CatchUp ID

curl -i -X DELETE \
  'https://docs.fluid.app/_mock/docs/apis/company.api/api/company/custom_catch_ups/{id}' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Responses

successful

Bodyapplication/json
catch_upobject
metaobject
Response
application/json
{ "catch_up": { "id": 0 }, "meta": { "request_id": "string", "timestamp": "2019-08-24T14:15:22Z" } }

generates custom catchup

Request

Bodyapplication/jsonrequired

Custom Catchups can be created in two main ways:

  1. Informative Catchup: This is the most common type of custom catchup. For instance, if the back office needs to share information with a user, they can use this API to create a catchup. An optional link can be included for further follow-up.

  2. Action-Based Catchup: This type of custom catchup allows you to add an existing catchup action. For example, you might create a catchup for an affiliate to notify them about specific behavior from one of their contacts. This behavior might not be covered by our existing 26 catchup matrix.

Types of CatchUp Action Supported For Custom CatchUp

  1. LinkRedirectionCatchUpAction: Use this action to redirect a user from the catchup card to a destination where other actions can be executed.
  2. SendSmsCatchUpAction: Use this action to allow users to send an SMS message to a contact from within a catchup card.
  3. ToDoCatchUpAction: Use this action to allow users to add a to-do item to their task list from within the catchup card.

Specific contact assigned to an affiliate should be provided to use the SendSmsCatchUpAction and ToDoCatchUpAction.

typestringrequired
Example: "custom_catch_up"
titlestringrequired
Example: "Talk to your favorite visitor."
headerstring
affiliate_idinteger(int32)required
Example: 1
actionsobject(CatchUpAction)required
Example: {"type":"LinkRedirectionCatchUpAction","action_prompt":"Craft a short friendly message to a visitor, visiting my site constantly and buying products."}
actions.​typestringrequired
Example: "LinkRedirectionCatchUpAction"
actions.​action_promptstringrequired
Example: "Craft a short friendly message to a visitor, visiting my site constantly and buying products."
curl -i -X POST \
  https://docs.fluid.app/_mock/docs/apis/company.api/api/company/catch_up/custom_catch_ups \
  -H 'Content-Type: application/json' \
  -d '{
    "type": "custom_catch_up",
    "title": "Update Your Bank Details",
    "description": "Your credit card is going to expire on 24th December. Please update your details.",
    "affiliate_id": 1,
    "actions": {
      "type": "LinkRedirectionCatchUpAction",
      "data": {
        "button_text": "View Back Office",
        "redirect_to": "https://fluid.app/back_office"
      }
    }
  }'

Responses

Created

Headers
Content-Typestring

The content type of the response

Example: "application/json"
Content-Lengthstring

The length of the response content in bytes

Example: "981"
X-Request-Idstring

A unique identifier for the request

Example: "b1b7bf86-146e-4c66-b4c6-ac6f0f9ddafa"
Bodyapplication/json; charset=utf-8
any
Response
application/json; charset=utf-8
{ "status": "success" }

Categories

Operations

Checkout

Operations

Collections

Operations

Companies

Operations

Company Countries

Operations

Contacts

Operations

Conversations

Operations

Countries

Operations

Currencies

Operations

Customer Notes

Operations

Customer Orders

Operations

Customers

Operations

DAM Query

Operations

Dam

Operations

Default MySites

Operations

Devices

Operations

Discounts

Operations

Display Settings

Operations

Domains

Operations

Drop Zones

Operations

Droplet Categories

Operations

Droplet Installations

Operations

Droplets

Operations

Enrollment Packs

Operations

Enrollments

Operations

Entities

Operations

Events

Operations

FairShare Order Journey

Operations

Feature Flags

Operations

File Resources

Operations

Fluid Pay

Operations

Form Elements

Operations

Forms

Operations

Global Embeds

Operations

Inventory Levels

Operations

Labels

Operations

Languages

Operations

Libraries

Operations

MCC Codes

Operations

Media

Operations

Messages

Operations

Metafield Definitions

Operations

Metafields

Operations

Mobile Widgets

Operations

Multi-Factor Authentications

Operations

Notifications

Operations

Onboarding

Operations

Onboarding Info

Operations

Order Fulfillments

Operations

Orders

Operations

Owners

Operations

Pages

Operations

Payment

Operations

Payment Accounts

Operations

Payment Integrations

Operations

Payments

Operations

Paypal

Operations

Points

Operations

Points Ledgers

Operations

Points Values

Operations

Posts

Operations

Product Bundles

Operations

Product Images

Operations

Product Subscription Plans

Operations

Products

Operations

Prompts

Operations

Public Assets

Operations

Public Companies

Operations

Public Drop Zones

Operations

Ranks

Operations

Recipients

Operations

Redirects

Operations

Refunds

Operations

Reps

Operations

Roles

Operations

Root Themes

Operations

Shares

Operations

Shop

Operations

Sitemap

Operations

Social Media

Operations

Subscription Plans

Operations

Subscriptions

Operations

System Monitoring

Operations

Tags

Operations

Tax Categories

Operations

Theme Region Rules

Operations

Tiles

Operations

Tracking Informations

Operations

Tree Nodes

Operations

Trees

Operations

Users

Operations

Variant Countries

Operations

Variant Images

Operations

Variant Inventory Levels

Operations

Variants

Operations

Warehouses

Operations

Webhook Events

Operations

Webhook Schemas

Operations

Webhooks

Operations

Webhooks Resources

Operations

affiliate

Operations

carts

Operations

checkout

Operations

enrollment-packs

Operations

events

Operations

fingerprint

Operations

lead

Operations

media

Operations

page

Operations

playlist

Operations

product

Operations

session

Operations

settings

Operations

url

Operations

widgets

Operations