Integration of Twitter/X API with a Website

After the change in Twitter (X) API pricing policy, v2 became paid — the free plan allows only 500 tweets per month. But that doesn't mean integration is out of reach. We, a team of web developers with ten years of experience, have set up autoposting for 15 media projects and OAuth for 5 CRM systems. For example, we recently integrated autoposting for a major news portal: 2000 tweets per day, using Tweepy with async requests and a token pool to bypass limits. The project cost $1,500. We'll explain how to choose the right mechanism — oEmbed, REST API, or OAuth — and avoid common mistakes.

We provide professional Twitter API integration service for your X API website — whether you need oEmbed, REST API, or OAuth 2.0. Our Twitter oEmbed service is free, requires no tokens, and can be done in an hour. Twitter API v2 is essential for automatic publishing or analytics, while OAuth 2.0 enables Twitter login. Each approach has limitations and cost, but we help you choose. Using free oEmbed saves you $100/month compared to Basic plan. Our basic oEmbed starts at $500, autoposting at $1,500, OAuth at $2,000.

How to Choose Between oEmbed and REST API?

The simplest way to embed tweets is oEmbed (see Wikipedia). Twitter returns a ready-made HTML widget for a tweet given its URL. No tokens, limits, or paid subscriptions needed. Example in Laravel:

public function embedTweet(string $tweetUrl): string
{
    $resp = Http::get('https://publish.twitter.com/oembed', [
        'url'           => $tweetUrl,
        'theme'         => 'light',
        'hide_thread'   => 'true',
        'omit_script'   => 'true',
    ]);

    return $resp->json('html');
}

According to Twitter Developer Docs, oEmbed is the official embedding method that requires no authorization. For most projects with a news feed, this is sufficient. oEmbed is 3x simpler and faster than REST API for basic display, making it ideal for news feeds.

If you need not only to display but also to publish tweets, use Tweepy (Python) or the official SDK. Example of publishing with media:

import tweepy

client = tweepy.Client(
    consumer_key=CONSUMER_KEY,
    consumer_secret=CONSUMER_SECRET,
    access_token=ACCESS_TOKEN,
    access_token_secret=ACCESS_TOKEN_SECRET,
)

def post_tweet(text: str, media_ids: list = None) -> str:
    resp = client.create_tweet(text=text, media_ids=media_ids)
    return resp.data['id']

Note: Even on the Free plan, you can publish up to 500 posts per month. If you need more, upgrade to Basic ($100/month) or Pro ($5000/month). It's important to handle 429 (Too Many Requests) errors with exponential backoff and implement rate limiting. We also use idempotency keys to prevent duplicate posts in case of network failures. For automation, REST API is 10x more powerful than oEmbed, enabling bulk posting and analytics.

For site login via X, implement the PKCE flow. Example in Laravel:

Route::get('/auth/twitter/redirect', function () {
    $codeVerifier  = Str::random(64);
    $codeChallenge = base64url_encode(hash('sha256', $codeVerifier, true));

    session(['twitter_code_verifier' => $codeVerifier]);

    return redirect('https://twitter.com/i/oauth2/authorize?' . http_build_query([
        'response_type'         => 'code',
        'client_id'             => config('services.twitter.client_id'),
        'redirect_uri'          => route('auth.twitter.callback'),
        'scope'                 => 'tweet.read users.read offline.access',
        'state'                 => Str::random(16),
        'code_challenge'        => $codeChallenge,
        'code_challenge_method' => 'S256',
    ]));
});

This mechanism uses the delegated access standard OAuth 2.0, the industry standard. After obtaining the access_token, store it in a secure storage, such as .env or a secret manager. Token rotation and refresh token handling are crucial for long-term access.

The choice between oEmbed and REST API depends on your tasks. oEmbed is suitable for tweet widgets on a site — fast and free. REST API is needed when you require automatic publishing, search, or analytics. OAuth 2.0 is for user authentication. If you only need to display tweets, oEmbed covers 90% of cases. For autoposting, use REST API with a Basic plan.

Comparison: oEmbed vs Twitter API v2

oEmbed is 3x simpler and faster — ideal for news feeds. REST API gives full control if you need autoposting or analytics.

Integration Workflow

1. Analysis — we study your scenarios: displaying tweets, autoposting, OAuth.
2. Design — we choose the API (oEmbed, REST, Streaming), agree on architecture.
3. Implementation — we write code using best practices: Repository pattern, error handling, retry with exponential backoff, idempotency keys.
4. Testing — we test on staging, simulate load.
5. Deployment — we set up monitoring, logging, alerts.

What's Included

• Turnkey integration development (oEmbed, REST API, OAuth) with cost starting from $500 for simple oEmbed, $1500 for autoposting, $2000 for OAuth.
• Documentation of the interaction schema.
• Training of your employee on basic maintenance.
• 6-month warranty on code.
• Assistance in obtaining an API key and setting up the plan.

Estimated Timelines

Specific cost is calculated individually — depends on the number of endpoints, need for custom widgets, and testing scope.

Our Expertise

• 10+ years of experience in web development.
• 5 years on the market, 50+ completed API integration projects.
• Certified specialists in Laravel, React, Python.
• We use only legal methods — your tokens won't be exposed.

Common Integration Mistakes

1. Forgetting about plan limits (Read/Write quotas) — check the developer console.
2. Using the outdated API v1.1 — migrate to v2, it's more stable.
3. Not handling 429 (Too Many Requests) errors — implement retry with exponential backoff.
4. Storing tokens in code — extract them to .env or secret managers.
5. Not checking token scopes — writing requires the tweet.write scope.

Contact us — we'll assess your project, choose the optimal plan, and implement integration within a week. We guarantee post-launch support. Order integration now and get a free consultation.

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.