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

Loops Campaigns API

Create, target, schedule and update email campaigns. 4 operation(s) in the Loops REST API v1 (OpenAPI 1.21.6).

Loops Campaigns API is one of 21 APIs that Loops publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Campaigns. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 2 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 1.21.6.

Requests are made against a single base URL, https://app.loops.so/api.

4 operations 2 paths 15 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.21.6
Base URL
https://app.loops.so/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Loops Campaigns API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (apiKey).

Paths & Operations 4

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

Campaigns 4

Create and manage email campaigns

GET
/v1/campaigns
List campaigns
listCampaigns 2 params → 200400401405
POST
/v1/campaigns
Create a campaign
createCampaign body → 201400401404405
GET
/v1/campaigns/{campaignId}
Get a campaign
getCampaign 1 param → 200400401404405
POST
/v1/campaigns/{campaignId}
Update a campaign
updateCampaign 1 param body → 200400401404405409

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are CreateCampaignResponse (12 properties), CampaignResponse (11 properties), CreateCampaignRequest (6 properties), Pagination (6 properties). Each schema is shown below with its type and property counts.

OptInCondition
object
Matches contacts by mailing-list opt-in status.
2 properties 2 required
CreateCampaignRequest
object
6 properties 1 required
AudienceFilterCondition
Pagination
object
6 properties 6 required
CampaignSchedulingRequest
object
When the campaign should send. timestamp is required and must be in the future when method is schedule, and must be omitted when method is now.
2 properties 1 required
PropertyCondition
object
Matches contacts by a property value.
4 properties 3 required
CreateCampaignResponse
object
12 properties 12 required
CampaignResponse
object
11 properties 11 required
CampaignScheduling
object
When the campaign is scheduled to send.
2 properties 2 required
UpdateCampaignRequest
object
At least one field must be provided.
6 properties
CampaignFailureResponse
object
1 property 1 required
AudienceFilter
objectnull
A tree of audience conditions combined with match.
2 properties 2 required
ListCampaignsResponse
object
2 properties 2 required
ActivityCondition
object
Matches contacts by their activity on a campaign or workflow.
5 properties 5 required
AudienceFilterInRequest
objectnull
A tree of audience conditions combined with match. Setting this without also providing audienceSegmentId clears any existing audienceSegmentId. When both are p…
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

loops-campaigns-api-openapi.yml Raw ↑

Other APIs Loops publishes across the network.

Loops API key API
Loops Audience segments API
Loops Campaign groups API
Loops Components API
Loops Configuration API
Loops Contact properties API
Loops Contacts API
Loops Email messages API
Loops Event patterns API
Loops Events API
Loops Mailing lists API
Loops Themes API
Where this information came from

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