{"pattern":"(\\w+)@(\\w+)\\.com","flags":"g","matched":true,"count":2,"matches":[{"match":"[email protected]","index":0,"groups":["ana","acme"],"named":null},{"match":"[email protected]","index":14,"groups":["bob","corp"],"named":null}]}
curl --location --request GET 'https://zylalabs.com/api/13159/regular+expression+tester+api/26705/test+regular+expression' --header 'Authorization: Bearer YOUR_API_KEY'
Após se cadastrar, cada desenvolvedor recebe uma chave de acesso à API pessoal, uma combinação única de letras e dígitos para acessar nosso endpoint de API. Para autenticar com a Regular Expression Tester API basta incluir seu token Bearer no cabeçalho Authorization.
| Cabeçalho | Descrição |
|---|---|
Authorization
|
Obrigatório
Deve ser Bearer access_key. Veja "Sua chave de acesso à API" acima quando você estiver inscrito.
|
Sem compromisso de longo prazo. Faça upgrade, downgrade ou cancele a qualquer momento. O teste gratuito inclui até 50 requisições.
(Economize 2 meses com cobrança anual 🎉)
Empresas líderes confiam em nós
Run regular expressions safely, even ones you do not trust. Every pattern is evaluated in an isolated worker with a hard time limit, so catastrophic backtracking is stopped cleanly instead of hanging your servers.
Useful for regular expression playgrounds and teaching tools, validating user supplied patterns before saving them, extracting fields from logs and documents, and debugging patterns in delivery pipelines.
The Test Regular Expression endpoint returns data indicating whether the regex matched the input text, the total match count, and detailed match information including matched text, positions, capture groups, and named groups.
Key fields in the response include "pattern" (the regex used), "flags" (regex flags), "matched" (boolean indicating a match), "count" (number of matches), and "matches" (an array of match details including "match", "index", "groups", and "named").
The response data is structured as a JSON object. It contains the regex pattern and flags, a boolean for match status, a count of matches, and an array of match objects, each detailing the matched text, its position, and any capture or named groups.
The endpoint provides information on whether the regex matched the input, the number of matches found, and detailed match data including the matched text, its position in the input, and any capture or named groups.
Os usuários podem personalizar suas solicitações especificando o padrão regex, o texto de entrada e flags opcionais (como 'g' para correspondências globais) nos parâmetros da consulta da solicitação GET para o endpoint
Casos de uso típicos incluem validar padrões regex fornecidos pelo usuário extrair campos específicos de logs ou documentos depurar padrões regex e criar playgrounds interativos de regex para fins educacionais
Users can utilize the returned data by analyzing the "matches" array to extract relevant information, such as using capture groups for further processing or displaying matched results in user interfaces.
Standard data patterns include simple matches like email addresses or phone numbers, as well as more complex patterns involving multiple capture groups. Users should expect variations in match counts based on the input text and regex complexity.