Finding an endpoint should be easier than scrolling through a long reference page. Sendar's documentation now has a dedicated interface that brings setup, language guides and the API reference into one consistent workspace.
Start with your integration
The new introduction explains the prerequisites: a Sendar account, a verified sending domain and a server-side API key. Quickstart cards take you to the Node.js, Next.js and Python guides. Existing guides for other languages remain available from the Guides section.
If you are moving from another provider, the migration hub remains linked in the sidebar. Read the compatibility notes before changing your production sending path. A refreshed interface does not change the API contract or make an unsupported transport available.
Find the right reference
The sidebar groups operations into sending, templates, audiences and broadcasts, and suppressions. HTTP method labels make it easier to distinguish reads from writes. Search filters documentation titles and descriptions, including language guides and endpoint summaries. Press Command-K or Control-K to focus it, or use the search field directly.
This is a navigation search, not an AI assistant or a full-text search of every paragraph. For exact request and response details, open the matching reference. The machine-readable OpenAPI specification and Markdown reference are also linked for tools and agents.
Read with less interruption
An on-page contents rail lets desktop readers jump between sections. Code examples retain their language choices and copy controls. Keyboard users can move between language tabs with the arrow keys, Home and End. On smaller screens, a collapsible menu keeps the article readable while leaving navigation within reach.
The documentation uses the same focused layout for signed-in and signed-out visitors. Existing reference URLs and endpoint anchors remain in place, so links in your project notes can still take you to the relevant material.
Try the updated workflow
Open the introduction, choose your application language, then consult the API reference for the fields your message needs. Keep credentials on your server and check the domain setup before sending. The redesign helps you find those instructions; it does not replace your application's validation, retry handling or delivery monitoring.
Documentation pages and guides are also rendered into the initial HTML so their content can be read without waiting for the application JavaScript. Search, the live contents rail and other interactive controls require JavaScript. If an example needs clarification, the integration support link is available at the end of each page.