Integrate Your Website with Discord: Notifications, Bots, OAuth2

You set up a Discord webhook, but notifications arrive late or not at all. Or OAuth2 returns an invalid scope error. These issues arise from misconfiguration or ignoring API rate limits. We solve such tasks daily — full Discord API integration with your site. Stack: Laravel 11, PHP 8.3, PostgreSQL, Redis. We automate notifications via webhooks, implement login via Discord (OAuth2), and role-gating for access control. Order an integration — prices start from $500 for basic webhook setup, up to $2500 for a full bot with custom logic. Cost is finalized after analysis.

Problems We Solve

Manual notification sending — an admin copies announcements by hand, forgets, or makes mistakes. Automation via webhooks eliminates human error. Complex authorization — users need to remember logins and passwords. OAuth2 via Discord simplifies login to one click. Role-gating — you need to give paid subscribers access to restricted sections. Discord API checks the user's role and dynamically grants access. Typical technical mistakes: incorrect scope in OAuth2, missing rate limit handling (50 requests per second), token leakage through logs or client code. Webhooks are set up 10 times faster than a bot, but a bot provides 5 times more capabilities — from automatic role assignment to moderation.

How to Avoid Common Errors When Integrating the Discord API

First mistake — incorrect scope. To get the user's email, always specify identify. To check roles, use guilds.members.read. Second — storing the Client Secret. It must be server-side only, never exposed in client code. Third — exceeding rate limits. Discord limits 50 requests per second per token. Use a queue (Redis) to send webhooks asynchronously. Fourth — wrong OAuth2 flow order: first exchange the code for a token, then use the token to fetch data. Do not mix stages.

How We Do It

We use the stack: Laravel 11 (PHP 8.3) for backend, MySQL/PostgreSQL, Docker for environment. Below is an example of webhook implementation for notifications:

class DiscordNotifier
{
    public function send(string $webhookUrl, array $embeds): void
    {
        Http::post($webhookUrl, [
            'embeds' => $embeds,
        ]);
    }

    public function announceNewArticle(Article $article): void
    {
        $this->send(config('services.discord.news_webhook'), [[
            'title'       => $article->title,
            'description' => $article->excerpt,
            'url'         => route('articles.show', $article->slug),
            'color'       => 0x5865F2,   // Discord Blurple
            'image'       => ['url' => $article->cover_url],
            'timestamp'   => $article->published_at->toIso8601String(),
            'footer'      => ['text' => 'My Site'],
        ]]);
    }
}

We configure a queue (via Redis) to process webhooks asynchronously, so as not to block the user's response.

How the OAuth2 Flow Works

OAuth2 is a standard authorization protocol that allows users to log in via third-party services (OAuth 2.0). In the case of Discord:

1. Register an application in the Discord Developer Portal and get a Client ID and Client Secret.
2. Set up a redirect URI to your site.
3. When the user clicks "Login with Discord", they are redirected to authorization, then back with a code.
4. The server exchanges the code for a token and fetches the user's data.

Example routes in Laravel:

Route::get('/auth/discord/redirect', function () {
    return redirect(
        'https://discord.com/api/oauth2/authorize?' .
        http_build_query([
            'client_id'     => config('services.discord.client_id'),
            'redirect_uri'  => route('auth.discord.callback'),
            'response_type' => 'code',
            'scope'         => 'identify guilds.members.read',
        ])
    );
});

Route::get('/auth/discord/callback', function (Request $request) {
    // Exchange code for token
    $tokenResp = Http::post('https://discord.com/api/oauth2/token', [
        'client_id'     => config('services.discord.client_id'),
        'client_secret' => config('services.discord.client_secret'),
        'code'          => $request->code,
        'grant_type'    => 'authorization_code',
        'redirect_uri'  => route('auth.discord.callback'),
    ])->json();

    // Fetch user data
    $user = Http::withToken($tokenResp['access_token'])
        ->get('https://discord.com/api/users/@me')
        ->json();

    // Check membership in server
    $member = Http::withToken($tokenResp['access_token'])
        ->get("https://discord.com/api/users/@me/guilds/{$guildId}/member")
        ->json();

    return redirect('/dashboard');
});

Choosing Between Webhooks and a Bot for Your Project

Webhooks are suitable for sending notifications: new articles, orders, registrations. They are simple to set up and do not require a persistent connection. Bots (Gateway API) are needed for interactive scenarios: role assignment, moderation, integration with external services. For example, a bot can automatically assign a premium role after payment on the site. If you only need notifications — go with webhooks. If two-way interaction is required — choose a bot. We help you decide during the analysis phase.

Work Process

Total: from 3 to 7 days depending on complexity.

What's Included

• Setting up Discord Webhooks for notifications (new articles, orders, registrations).
• Implementing OAuth2 authorization with role checking.
• Developing a bot for automatic role assignment.
• Integration documentation and post-launch support.
• 30-day guarantee of functionality and bug fixes.

Comparison of Integration Methods

Our team has over 10 years of experience in web development and dozens of successful Discord integrations. We guarantee stable operation and timely API updates. The time saved on manual notifications pays off within the first weeks. Get a consultation — contact us to discuss details. Order an integration, and we'll set it all up for your site.

API Development with REST, GraphQL, WebSocket, and tRPC

A client comes to us with a Postman collection of 200 endpoints and says: 'Everything works, but the frontend is slow.' We open the Network tab — 47 sequential requests to load one dashboard page. Each one waits for the previous. This is not a server speed issue — it's an API architecture problem. With 10 years on the market, we've redesigned dozens of such integrations, and we guarantee: the right protocol and contract solve the problem at its root.

When REST stops being enough

REST works well for simple CRUD operations. But as soon as a mobile app appears alongside the web interface, over-fetching begins: the mobile app requests /api/users/123 and gets a 4KB object, but only needs name and avatar. Multiply that by a list of 50 users — 200KB traffic instead of 8KB.

GraphQL solves this with selection sets. The client describes exactly the fields it needs, and the server returns only those. On a project with React Native + Next.js, we migrated from REST to Apollo Server: payload size on the main screen dropped from 340KB to 28KB — a 92% traffic savings. Our certified engineers confirm: the typical pain when adopting GraphQL is N+1 query. A resolver for the author field on a post calls SELECT * FROM users WHERE id = ? for each post in the list. On a page with 20 posts — 21 database queries. Solved with DataLoader — it batches queries and turns them into one SELECT * FROM users WHERE id IN (...).

What is tRPC and how is it better than REST/GraphQL?

If the entire stack is TypeScript (Next.js + Node/Bun), tRPC removes a whole layer of problems. You define a procedure on the server — the client gets full type-safety automatically, without code generation and without Swagger. Renamed a field in the Zod schema — TypeScript highlights all places on the frontend where it's used. tRPC reduces code by 2 times compared to REST + Swagger + openapi-typescript: no need to maintain a separate specification and generate types — everything is inferred from runtime validators. However, tRPC is not suitable if the API is consumed by third-party clients or mobile apps in other languages — in such cases we use GraphQL or REST with OpenAPI specification.

WebSocket and real-time: when SSE, when WS?

HTTP polling every 5 seconds is an illusion of real-time with up to 5 seconds delay and useless server load. For chats, live notifications, collaborative editing — WebSocket or Server-Sent Events. SSE is a one-way stream from server to client, works over ordinary HTTP, automatically reconnects. Suitable for notifications, data streaming, progress bars. WebSocket is bidirectional, needed for chats and collaborative features. Experience shows: 80% of 'real-time' tasks are solved with SSE, not WebSocket — fewer infrastructure complexities.

A typical mistake: opening a WebSocket connection for each page component. On one project, the dashboard opened 12 parallel WS connections. The correct approach is one connection manager at the application level, subscriptions through it. In our work results, we always transfer the connection scheme and a ready solution.

Swagger / OpenAPI as a contract

Documentation written after the fact becomes outdated the day after release. We write the OpenAPI 3.1 specification before development starts; it becomes the contract between frontend and backend. The frontend generates types via openapi-typescript, the backend validates incoming data using generated schemas. Contract deviation from implementation is caught on CI, not during review. For Laravel — l5-swagger or dedoc/scramble. For Node.js — @fastify/swagger or Zod + zod-to-openapi.

How to properly authenticate an API?

JWT with long-lived access tokens without rotation is a source of problems when compromised. The correct scheme: access token for 15 minutes, refresh token for 30 days with rotation on each use. Refresh token stored in an httpOnly cookie, access token in memory (not in localStorage). For inter-service communication — API Keys with scope limitations or mTLS. OAuth 2.0 with PKCE for public clients (SPA, mobile).

How to handle versioning and backward compatibility?

Breaking changes in an API without versioning break clients. Three approaches we use in projects:

We guarantee backward compatibility through automated checks (oasdiff) on CI.

How we develop APIs: step-by-step plan

1. Analysis — audit of current integrations, data schema compilation, protocol selection (REST/GraphQL/tRPC/WebSocket).
2. Contract design — OpenAPI or SDL (GraphQL) before the first line of code.
3. Development — implementation per contract, unit tests for each endpoint.
4. Load testing — k6: 500 virtual users, 10 minutes, p95 latency ≤ 200ms.
5. Deployment — CI/CD with backward compatibility check, automatic documentation publication.
6. Team training — handover of Postman collection or Playground, connection instructions.

What is included (deliverables)

• OpenAPI 3.1 specification (or SDL for GraphQL).
• Generated client types for TypeScript / Dart / Kotlin.
• Set of automated tests covering all endpoints (unit + integration).
• Load tests (k6) and report (p50/p95/p99 latency, RPS).
• Documentation in Swagger UI / Redoc / GraphiQL.
• Team training (2–4 hour workshop).
• Support for 30 days after delivery (per contract).

Our experience

• 10+ years in the API development market.
• 200+ completed projects (REST, GraphQL, WebSocket, tRPC).
• 50+ certified engineers (AWS, Kubernetes, API Design).
• Traffic savings averaging 85% when migrating from REST to GraphQL for mobile apps.
• 100% backward compatibility — not a single broken client in the last 3 years.

Timeline

API development for a typical SaaS project with 30–50 endpoints: from 3 to 8 weeks depending on business logic complexity and number of external integrations. Migration of an existing REST API to GraphQL: from 2 to 6 weeks. Adding a WebSocket layer to an existing backend: from 1 to 3 weeks. Cost is calculated individually after an audit. Get a consultation — contact us to discuss your project.