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

DEV Community segments API

The segments API from DEV Community — 5 operation(s) for segments.

DEV Community segments API is one of 19 APIs that DEV Community publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 7 operations across 5 paths, and defines 3 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against a single base URL, https://dev.to/api.

7 operations 5 paths 3 schemas 1 DELETE3 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://dev.to/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

DEV Community segments API declares 1 security scheme for authenticating requests. An API key is passed in the header as api-key (api-key). By default, every request must be authenticated.

  • api-key — API Key authentication. Authentication for some endpoints, like write operations on the Articles API require a DEV API key. All authenticated endpoints are COR…

Paths & Operations 7

Across 5 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

segments 7
GET
/api/segments
Manually managed audience segments
getSegments 1 param → 200401
POST
/api/segments
Create a manually managed audience segment
createSegment → 201401
GET
/api/segments/{id}
A manually managed audience segment
getSegment 1 param → 200401404
DELETE
/api/segments/{id}
Delete a manually managed audience segment
deleteSegment 1 param → 200401404409
GET
/api/segments/{id}/users
Users in a manually managed audience segment
getUsersInSegment 2 params → 200401404
PUT
/api/segments/{id}/add_users
Add users to a manually managed audience segment
addUsersToSegment 1 param body → 200401404422
PUT
/api/segments/{id}/remove_users
Remove users from a manually managed audience segment
removeUsersFromSegment 1 param body → 200401404422

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are User (11 properties), Segment (3 properties), SegmentUserIds (1 property). Each schema is shown below with its type and property counts.

Segment
object
A manually managed audience segment
3 properties
User
object
The representation of a user returned in a list
11 properties
SegmentUserIds
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

devto-segments-api-openapi.yml Raw ↑

Other APIs DEV Community publishes across the network.

DEV Community agent_sessions API
DEV Community articles API
DEV Community billboards API
DEV Community comments API
DEV Community display ads API
DEV Community followed_tags API
DEV Community followers API
DEV Community organizations API
DEV Community pages API
DEV Community podcast_episodes API
DEV Community profile images API
DEV Community reactions API
Where this information came from

This is an independent, third-party profile of DEV Community segments 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.