Skip to main content
This guide covers the key concepts you need to integrate the mutes endpoints into your application.

Authentication

Mutes endpoints require user authentication to access private mute lists:
App-Only authentication is not supported. You must authenticate on behalf of a user.

Required scopes (OAuth 2.0)


Endpoints overview


Fields and expansions

Default response

Available fields

Example with fields

cURL

Pagination

For users with large mute lists, results are paginated:
cURL

Pagination guide

Learn more about pagination

Behavior differences

Muting vs Blocking

Muting is private — the muted user is not notified and cannot tell they’ve been muted.

Error handling


Next steps

Quickstart

Make your first mutes request

Blocks

Block users instead of muting

API Reference

Full endpoint documentation

Sample code

Working code examples