POST /extract_urls_emails • Credits: 0.5 credits per call

Extract URLs & Emails scans a block of text and returns every URL and every email address in that text. The response holds a separate urls array and a separate emails array, plus counts and comma-joined strings. Each call costs 0.5 credits ($0.01).

Extract URLs & Emails is a text parser. It takes text that you already hold, such as an email body, a CRM note, or a scraped page fragment. The endpoint runs two regular expressions over that text. One pattern matches email addresses, and one pattern matches URLs. Extract URLs & Emails fetches no page and calls no external provider, so the result depends only on the text in the request body. The endpoint removes duplicate matches and drops a URL that points at a private network address or that carries a cross-site scripting pattern.

CAUTION: Each Extract URLs & Emails call costs 0.5 credits. A call that finds no URL and no email address also costs 0.5 credits.

Extract URLs & Emails accepts one parameter. It accepts no query parameter and no path parameter.

The block below is an example response for the request body {"text": "Contact us at [email protected] or visit https://acme.com/pricing"}.

The urls array holds acme.com because the URL pattern also matches the host name inside [email protected]. The section "What does Extract URLs & Emails pull out of an email signature?" explains that behavior.

Extract URLs & Emails returns this flat object, with no data envelope. Like every RichAPI response, it also carries richapi_meta with the request ID and the credits charged and remaining.

An email signature is the common case for this endpoint. The text below is a messy signature block. It holds a personal address, two role addresses in different letter case, two full URLs, and one bare host name.

Send that block as one JSON string. The request body below carries the same text with \n for each line break.

The response for that request body is the example below.

The table below maps each part of the signature to the result.

CAUTION: An email address also adds entries to the urls array. The URL pattern matches the host name after the @ sign. It also matches a local part that holds a dot. Filter the urls array against the emails array before you store the result.

The two snippets below remove those entries. Each snippet reads the response object data from the code sample above.

Extract URLs & Emails compares every match in lower case. The first form in the text wins, and the response keeps the original letter case of that first form. [email protected] before [email protected] therefore returns [email protected] alone. Both arrays keep the order of first appearance in the text. Extract URLs & Emails sorts nothing and reorders nothing. The urls_and_emails array holds the whole urls array first, then the whole emails array.

Extract URLs & Emails removes an unsafe or invalid URL candidate before it builds the urls array. A dropped candidate appears in no field of the response.

The filter protects your systems against server-side request forgery and cross-site scripting. The emails array passes through no such filter.

Extract URLs & Emails parses text. Website Email Extractor fetches a live page. Extract URLs & Emails takes text that you already hold, and it returns the URLs and the email addresses inside that text. Website Email Extractor takes one website URL, crawls up to 10 pages of that website, and returns the addresses that the website publishes.

To read a live website, send a Website Email Extractor request. To parse text that you already hold, send an Extract URLs & Emails request. A common pattern combines the two: scrape a page with the Web Scraper endpoint, then send the returned text to Extract URLs & Emails.

Extract URLs & Emails costs 0.5 credits per call. At $0.02 a credit, the rate on the 1,000 and 5,000 credit packs, one call costs $0.01. Larger packs cost less per credit. The credit count does not change with the length of the text and does not change with the number of matches. RichAPI charges the credits on a 200 response only.

Every error response holds an error field with a text message.

RichAPI charges no credit for a 400, 401, 403, 404, 405, 429 or 500 response.

No. Extract URLs & Emails sends no HTTP request and opens no page. It reads only the text in the request body. A URL in the urls array is a string match, not a confirmed live page.

No. The urls array and the emails array hold each match one time. The comparison runs in lower case, and the first form in the text wins, so [email protected] and [email protected] return one entry.

The URL pattern matches a bare host name, and every email address holds a host name after the @ sign. The pattern also matches a local part that holds a dot, as in [email protected]. Filter the urls array against the emails array to remove those entries.

Yes. Every 200 response costs 0.5 credits, and an empty result is a 200 response with total_count set to 0. RichAPI charges no credit for a 4xx error and no credit for a 5xx error.

The URL pattern stops at a space character, at a line break, and at the characters <, >, " and '. It stops at no other punctuation. The text visit https://acme.com/pricing. therefore returns https://acme.com/pricing. with the full stop. Trim the trailing punctuation in your own code.

One call holds up to 10,485,760 characters (10 MB) in the text parameter. A longer value returns 400 and costs no credit.

No. Extract URLs & Emails matches URLs and email addresses only. To parse a phone number, send the number to the /normalize_phone endpoint, which also costs 0.5 credits per call.