Dev.to Organization Members API
The people in a Dev.to organization, returned as the same user objects as the account route.
GET /v1/dev-to/organization/members1 credit Failed requests are free
About this endpoint
GET /v1/dev-to/organization/members?username=mlh returns members, a page of user objects with id, username, name, bio, location, websiteUrl, twitterUsername, githubUsername, avatarUrl and joinedOn. Use page and limit to walk the list, up to 1000 members per request.
When the organization does not exist, lookupStatus is not_found, members is empty and page.hasMore is false. An organization with no members also returns an empty list, so check the organization route when the difference matters.
Dev.to Organization Members API FAQ
Are the members full user objects?
Yes. Each member uses the same fields as GET /v1/dev-to/user, so one parser handles both routes.
How many credits does a members page cost?
Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth. Each paginated page is a separate billed request.
How is the list ordered?
The order is the one Dev.to serves for the organization. Do not assume alphabetical or join-date order, and use page.nextPage to continue.
What does lookupStatus mean here?
not_found means the organization does not exist and the list is empty. found means the organization exists, and the list can still be empty for an organization with no members.