Connect Brilliant Directories

Brilliant Directories needs your site URL, an API key generated in the Developer Hub, and the numeric member user ID that should own published posts. API keys are shown only once.

Last updated 1 day ago

Three values, and one of them is only shown once.

Available on every plan.

What you Need

  • Your Brilliant Directories site URL.
  • An API key from the Developer Hub.
  • The numeric member user ID that should own posts.

Step 1: Generate an API Key

In your Brilliant Directories admin, open Developer Hub → Generate API Key.

Copy it immediately. Keys are shown only once. If you lose it, generate a new one.

Step 2: Find the Member User ID

This is the numeric ID of the member who should own the posts NarraSEO publishes. Find it in Members, either in the members list or on the member's profile.

It is a number, such as 42, not a name or an email address.

Choose deliberately. Every article NarraSEO publishes is attributed to this member, so use the account that should appear as the author.

Step 3: Enter the Credentials

  1. Open Sidebar → Integrations.
  2. Find Brilliant Directories under Publishing & CMS.
  3. Fill in the three fields:

Field

Example

Site URL

https://www.example.com

API key

The key from step 1

Member user ID

42

  1. Select Connect Brilliant Directories.

Step 4: Verify

Select Verify connection. On success you see "Brilliant Directories connection verified."

On failure: "Could not verify the Brilliant Directories connection. Check the site URL and API key."

Publishing Options

Brilliant Directories has one option the other platforms do not: Post type, described as "Choose the Brilliant Directories post type (for example Blog) for this article."

Set this when you publish so the article lands in the right content type.

Otherwise it uses the standard status options and the Featured image and Article title toggles.

If it Will Not Connect

You lost the API key. Keys are shown once. Generate a new one in the Developer Hub.

The member user ID is not numeric. It wants the number, not the member's name or username.

The site URL is wrong. Use the address your site is actually served on, matching your www setup.

The API key was regenerated. Generating a new key invalidates the old one. Reconnect with the new key.

Notes

Regenerating an API key in the Developer Hub is the way to revoke access, since it invalidates the previous key.

Posts are attributed to the member user ID you supplied. Changing it changes the author for future posts only.

The connection is per project.