Is API TESTING possible in Cypress?

Most developers think Cypress is only for clicking buttons and filling forms. It is not. Cypress can test your entire API layer — requests, responses, headers, status codes, and even stubbed network traffic — without a browser in the loop. If you are doing QA or backend development in 2026, this is a capability you need to know.

Yes, Cypress Can Do API Testing

• cy.request() — makes direct HTTP calls to your API, completely independent of the browser UI. Think of it as a scriptable HTTP client inside your test suite.
• cy.intercept() — sits between your frontend and your backend, letting you spy on, assert against, modify, or fully stub every network request your application makes.

cy.request() — Direct API Testing

// Basic GET request
cy.request('GET', '/api/users').then((response) => {
  expect(response.status).to.eq(200)
  expect(response.body).to.have.length.greaterThan(0)
})

// POST with body and headers
cy.request({
  method: 'POST',
  url: '/api/users',
  headers: {
    'Content-Type': 'application/json',
    'Authorization': 'Bearer my-token'
  },
  body: {
    name: 'Jane Doe',
    email: '[email protected]'
  }
}).then((response) => {
  expect(response.status).to.eq(201)
  expect(response.body).to.have.property('id')
  expect(response.body.email).to.eq('[email protected]')
})

// DELETE and assert 204
cy.request('DELETE', '/api/users/1').its('status').should('eq', 204)

• response.status — HTTP status code
• response.body — parsed response body (JSON auto-parsed)
• response.headers — response headers
• response.duration — how long the request took
• response.requestHeaders — the headers that were sent

cy.intercept() — Network Interception and Stubbing

// Spy on a request and assert after
cy.intercept('GET', '/api/products').as('getProducts')
cy.visit('/products')
cy.wait('@getProducts').then(({ request, response }) => {
  expect(response.statusCode).to.eq(200)
  expect(response.body).to.be.an('array')
})

// Stub a response with fixture data
cy.intercept('GET', '/api/users', { fixture: 'users.json' }).as('getUsers')
cy.visit('/dashboard')
cy.wait('@getUsers')
cy.get('[data-testid="user-list"]').should('have.length', 3)

// Simulate error state
cy.intercept('POST', '/api/orders', {
  statusCode: 500,
  body: { error: 'Internal server error' }
}).as('failedOrder')
cy.visit('/checkout')
cy.get('[data-testid="submit-order"]').click()
cy.wait('@failedOrder')
cy.get('[data-testid="error-message"]').should('be.visible')

// Modify a response on the fly
cy.intercept('GET', '/api/config', (req) => {
  req.reply((res) => {
    res.body.featureFlag = true
    return res
  })
})

What You Can Test with Cypress API Testing

Cypress vs Other API Testing Tools

Common Patterns in Real QA Workflows

beforeEach(() => {
  cy.request('POST', '/api/test/reset-db')
  cy.request('POST', '/api/users', { name: 'Test User', email: '[email protected]' })
})

// Faster than typing into login form every test
cy.request('POST', '/api/auth/login', {
  email: '[email protected]',
  password: 'password123'
}).then(({ body }) => {
  window.localStorage.setItem('token', body.token)
})
cy.visit('/dashboard')

// Test the loading skeleton
cy.intercept('GET', '/api/data', (req) => {
  req.reply({ delay: 2000, body: [] })
})
cy.visit('/page')
cy.get('[data-testid="skeleton"]').should('be.visible')

cy.intercept('POST', '/api/checkout').as('checkout')
cy.get('[data-testid="buy-now"]').click()
cy.wait('@checkout').its('request.body').should('deep.include', {
  productId: 'abc-123',
  quantity: 1
})

Cypress API Testing and the QA Developer Path

Start Building Real QA and Backend Skills

Frequently Asked Questions