Полная документация ниже — автоматически из репозитория svjszn/bitrix24-api-skill (ветка master). Оригинальные материалы проекта распространяются на условиях его лицензии.

bitrix24-rest-api

A Claude Code Skill with foundational, empirically-verified knowledge for calling the Bitrix24 REST API from a backend service: auth modes (inbound webhook vs. OAuth app), the "HTTP 200 with an error body" gotcha, inconsistent list-response shapes, a sane retry policy, and rate limits.

This isn’t a client library — it’s a skill file (SKILL.md) that an AI coding agent loads into context before writing or debugging Bitrix24 integration code, so it doesn’t have to relearn the same gotchas from scratch (or from stale blog posts) every time.

Why

The Bitrix24 REST API is old, widely used, and full of behavior that’s easy to get wrong on a first pass — silent-success-shaped errors, non-uniform list responses, undocumented auth quirks. Most of what’s in this skill was confirmed against a real portal, not just copied from docs, and is dated so you can judge whether it might have drifted.

What’s covered

• Inbound webhook vs. OAuth local/marketplace app — when each is required, and the actual (undocumented) shape of the ONAPPINSTALL install payload
• Why you must always decode the response body and check for an error key, even on HTTP 200
• Why list-method responses aren’t a fixed shape (crm.duplicate.findbycomm returns an object on a hit, an empty array on a miss)
• A retry policy: what’s safe to retry (network errors, 5xx, 429/503) vs. what isn’t (any decoded error, any 4xx)
• How to diagnose insufficient_scope errors, and why the generic scope method can’t be trusted to introspect webhook permissions
• Rate limiting (leaky-bucket, per-portal/webhook, 503 QUERY_LIMIT_EXCEEDED)
• A documented Bitrix24 footgun: Lead auto-conversion can silently orphan a manually-linked Deal
• A working set of common CRM/task methods (crm.lead.add, crm.deal.*, crm.timeline.comment.*, crm.status.list, tasks.task.add, etc.) with the non-obvious parts called out

See skills/bitrix24-rest-api/SKILL.md for the full content.

Related skill

bitrix24-open-lines-bot builds on this one for the specific case of a chatbot inside a Bitrix24 Open Line (imbot.v2 / imopenlines).

Using this skill

The skill itself lives in skills/bitrix24-rest-api/.

Claude Code: copy or symlink that directory into your skills path (e.g. .claude/skills/bitrix24-rest-api/ for a project-local skill, or the equivalent global skills directory), or clone this repo and point at it directly:

git clone https://github.com/soajv/bitrix24-api-skill.git
cp -r bitrix24-api-skill/skills/bitrix24-rest-api .claude/skills/bitrix24-rest-api

Other agents/tools: skills/bitrix24-rest-api/SKILL.md is plain Markdown with a YAML frontmatter header (name, description) — feed it into any system prompt or context-loading mechanism that accepts freeform reference material.

Contributing

Corrections and additional confirmed gotchas are welcome. Please:

• Verify claims against a real portal where possible, and say what you tested and when (Bitrix24’s behavior does drift over time).
• Cite the specific official docs page you’re relying on, if any.
• Keep the tone of existing entries: state the behavior, the evidence for it, and how to work around it — not just a link.

Disclaimer

This project is unaffiliated with, and not endorsed by, Bitrix24 or 1C-Bitrix. "Bitrix24" is a trademark of its respective owner. Information here reflects behavior observed as of the dates noted in the text and may not be current — always cross-check against official docs for anything security- or billing-sensitive.

License

MIT