Enrich selected Excel rows from the sidebar
The GenderAPI Excel add-in lets you choose a name, email or username column and write results into mapped worksheet columns. Use the sidebar for a controlled row range, or the separate GENDER.FROM_* functions for cell-based calculations.
The native Excel client uses the legacy API fields. It does not return the direct REST V2 data and meta objects; keep existing workbook mappings aligned with the add-in's actual output.
Configure a small row range first
- Install GenderAPI from its Microsoft listing and open its task pane in your workbook. Review the document-access permissions and any organization restrictions.
- Save your GenderAPI key through the add-in and verify that the intended account has credits.
- Choose the name, email or username method and the matching source column. Set a small start and end row range, excluding headers.
- Map the gender destination and optional probability, country and found-name columns. Keep each output separate from the source data.
- Set country context only when it is reliable for the data you are processing. Review the chosen settings and run the sample.
- Inspect resolved, unresolved and failed rows before extending the range. Keep a copy of the original workbook data.
Choose input, context and result columns
| Setting | Type | Description |
|---|---|---|
| API key | Account credential | Saved using the add-in's key control; do not place it in ordinary workbook cells. |
| Method and source | Choice plus column | Name, email or username paired with its source column. |
| Row range | Row numbers | Start with a small range without the header row. |
| Country filter | Optional country or column | Supply known country context; it is not a request for verified personal location. |
| Output columns | Column references | A gender destination and optional probability, country and found-name destinations. |
Read the native result columns
Keep your original input beside the result. A name-based association does not establish a person's self-declared gender, and a returned country is not verified residence or nationality.
- Inspect an ordinary result, an ambiguous input and a failed operation before processing a full dataset.
- A blank cell, the text null and a formula error are different spreadsheet values. Normalize unknown results deliberately without hiding errors.
- Use a neutral fallback for unknown or uncertain records. Keep supplied profile information separate from inferred columns.
| Output | Typical type | How to use it |
|---|---|---|
| Gender | Text or unresolved value | Retain male or female only for a successful result. Preserve an unresolved value as unknown; review error text separately. |
| Probability | Number, when available | A legacy confidence signal. It is not the V2 confidence field or a measured accuracy rate for your dataset. |
| Country | Text, when available | Context returned by the lookup. Keep it separate from a customer's verified country. |
| Found or normalized name | Text, when available | The name used or extracted during processing. Review it for ambiguous emails and usernames. |
Plan for credits, limits and repeated runs
A registered free GenderAPI account includes 200 credits per day. Credits are an account balance, not a promise of 200 successful results in every workflow. Check the selected key's balance and the tool's current processing options before starting.
Native add-ons and file jobs have their own processing paths. The REST V2 batch limit, AI options and per-request billing fields do not automatically apply to them. A repeated run or recalculation can submit fresh work; do not assume it is free.
Start with a small sample, retain completed results, and review the failed rows before rerunning. If you only need to repair a later export or destination update, reuse the results you already have.
Choose the data you share
The spreadsheet integrations transmit values needed for lookups and require permission to work with the selected document. Review access to the workbook, the connected account and the destination columns before processing personal data.
Keep API keys in the add-on's settings rather than ordinary cells, screenshots or shared examples. The published privacy policy describes input handling, retention and logs; spreadsheet integration does not mean that data remains entirely on your device.
When to use the direct V2 API
Use a separate HTTP integration when your application needs explicit AI options, per-item status, source, confidence kind and usage information from V2. Follow the V2 request and response contract; adding V2 field names to a native formula or existing add-on does not change that client's behavior.
Frequently asked questions
Can I analyze emails and usernames in Excel?
Yes. Choose the corresponding method in the sidebar and map the matching input column. Inspect the returned name and unresolved outcomes before using the result.
Should I use the sidebar or a formula?
Use the sidebar to process a chosen range and write mapped values. Use the GENDER.FROM_* formulas when you want calculations tied to cell inputs and understand recalculation behavior.
Does functions_v2.js mean the add-in uses REST V2?
No. That is an Excel client asset name. The public formula asset reviewed for this guide calls legacy API endpoints and reads their legacy response fields.
Are predictions verified customer attributes?
No. Keep inferred results separate from information supplied by the customer and use a neutral fallback for unknown or uncertain records.
Reference sources
This guide and its reference sources were reviewed on . Use the platform references for setup details and the linked API documentation for a separate V2 integration.