API Reference

# Verify an RFC

Confirm that an RFC is registered with SAT, or that an RFC, name, and postal code match SAT's record as CFDI 4.0 requires, in a single round trip.

POST

`/v1/rfc/verify`

Two modes depending on what you submit. Both complete in 1 to 2 seconds.

## Mode 1: RFC only (padrón check)

Submit just the RFC to confirm it is registered and active with SAT. Use this to validate any RFC quickly without needing the customer's name or postal code.

curl

```bash
curl -X POST https://rfccheck.com/v1/rfc/verify \
  -H "x-api-key: rfc_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"rfc": "ACME010101AAA"}'
```

## Mode 2: RFC + name + zip (full combo)

Submit all three fields to confirm a complete combination. Use this to verify customer-supplied data before issuing an invoice, or to re-validate an existing record.

curl

```bash
curl -X POST https://rfccheck.com/v1/rfc/verify \
  -H "x-api-key: rfc_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "rfc": "ACME010101AAA",
    "name": "ACME CONSULTORES",
    "zip": "06600"
  }'
```

Provide name and zip together, or neither. Providing only one is rejected with 422.

To see which state, municipality, and colonias a zip code covers, use [`/geo/zip`](https://mexcheck.com/docs/endpoints/geo-zip) on MexCheck, with this same API key.

## Response (200)

200 OK

```json
{
  "rfc": "ACME010101AAA",
  "valid": true,
  "message": "RFC válido, y susceptible de recibir facturas"
}
```