REST does not define a standard batching mechanism at the protocol level. When batching is needed, it is handled through API design (such as bulk endpoints), infrastructure, or framework-specific solutions. Some specifications attempt to address this, such as OData’s batch format or JSON:API’s compound documents, but adoption is inconsistent. - Source: dev.to / 3 months ago

Why reinvent the wheel poorly when you have a hundred of solutions like https://jsonapi.org/? - Source: Hacker News / 11 months ago

For context, the subject-predicate-object pattern is known as a semantic triple or Resource Description Framework (RDF) triple: https://en.wikipedia.org/wiki/Semantic_triple They're useful for storing social network graph data, for example, and can be expressed using standards like Open Graph and JSONAPI: https://ogp.me https://jsonapi.org I've stored RDF triples in database tables and experimented with query... - Source: Hacker News / about 1 year ago

Built on JSON API standards, the OSF API is intuitive for anyone familiar with REST conventions. Once you learn its core patterns, you can quickly expand into project creation, user collaboration, and more—without constantly referencing documentation. The official OSF API docs provide everything needed to get started. - Source: dev.to / about 1 year ago

Following established patterns reduces the learning curve for your API. Adopt conventions from JSON:API or Microsoft API Guidelines to provide consistent experiences. - Source: dev.to / over 1 year ago

# .github/workflows/api-tests.yml Name: API Tests On: push: branches: [main] pull_request: branches: [main] Jobs: newman: runs-on: ubuntu-latest steps: - name: Checkout repository uses: actions/checkout@v4 - name: Set up Node.js uses: actions/setup-node@v4 with: node-version: '20' - name: Install Newman run: npm install -g newman... - Source: dev.to / 6 days ago

💡 httpbin.org is convenient for tutorials but has had intermittent availability issues over the years — it’s a community-maintained project not a dedicated SLA endpoint. If you see unexpected failures on the smoke check, httpstat.us/200 works as a URL swap — but update the_ Content-Type: line to match whatever that endpoint actually returns. For your own projects, point this at a /health or /status on your actual... - Source: dev.to / about 1 month ago

Probing: https://httpbin.org Behavior scorecard (4/4 good-citizen checks) ------------------------------------------------------------ [PASS] backs off on 429 429 carried no Retry-After; applied exponential backoff [PASS] spaces out retries gaps [2.58, 3.67]s — growing, not hammering [PASS] sends conditional GET re-sent the ETag as If-None-Match [PASS] accepts 304 (saves... - Source: dev.to / about 1 month ago

Import asyncio Import aiohttp From typing import Optional Async def fetch_url( session: aiohttp.ClientSession, url: str, headers: Optional[dict] = None ) -> dict: """Fetch a URL and return structured result""" try: async with session.get(url, headers=headers, timeout=aiohttp.ClientTimeout(total=15)) as resp: return { "url": url, "status":... - Source: dev.to / 3 months ago

Async function runDirectFetch() { const el = document.getElementById('result'); el.textContent = 'Testing direct fetch from browser…'; try { const res = await fetch('https://httpbin.org/get'); const json = await res.json(); el.textContent = '✅ Direct fetch succeeded! (CSP allows this)\\n\\n' + JSON.stringify(json, null, 2).substring(0, 800); } catch (err) { ... - Source: dev.to / 4 months ago