Skip to content

Add Firmaradar Independent Publisher submission#4205

Open
Tiwas wants to merge 4 commits into
microsoft:devfrom
Tiwas:firmaradar-independent-publisher
Open

Add Firmaradar Independent Publisher submission#4205
Tiwas wants to merge 4 commits into
microsoft:devfrom
Tiwas:firmaradar-independent-publisher

Conversation

@Tiwas

@Tiwas Tiwas commented May 27, 2026

Copy link
Copy Markdown

Connector certification submission

Description

Enrichment platform for Norwegian company intelligence — built to
extend other services with KYC, AML, credit, ownership and risk
insights through AI/agent flows, REST APIs and a web UI. Fuses data
from multiple authoritative sources (Brønnøysundregistrene,
Skatteetaten, foreign PEP and sanctions registers, distress signals,
public-grants registries) and layers proprietary enrichment on top:
distress classification, risk scoring, fuzzy person-matching,
group-structure analytics and audit-grade compliance pipelines. 22
operations across 7 functional areas, with stable contracts shared
with our MCP server, n8n nodes and Make.com app.

Why Independent Publisher

Firmaradar AS is a small Norwegian company providing a paid API. The
service is not in the Verified Publisher program yet — we want to be
listed in the catalog so Power Automate users can discover Firmaradar
without manual custom-connector setup. Audience includes both Norwegian
primary users (banks, KYC teams, vendor-risk) and international users
with Norwegian counterparties — Power Automate is a natural fit for
both.

Testing evidence

  • Connector deployed to publisher's Default Environment via paconn create 2026-05-27 (connector id shared_firmaradar-5ff0f17abe639fa74e-5fe9cb345f39a094ff).
  • Tested 3 operations end-to-end via Custom Connector editor's Test
    tab. All returned HTTP 200 with expected data (screenshots attached):
    • getCompany (orgnr=923609016) — full Equinor ASA profile
    • searchCompanies (q=Equinor) — paginated results, multiple hits
    • checkForetakIVanskeligheter (orgnr=923609016) — FIV status,
      schema validation succeeded
  • paconn validate returns no errors.
  • Known minor warnings: searchCompanies returns antall_ansatte and
    total_count as JSON strings but swagger declares integer. Does
    not block usage; will be reconciled in a future swagger update.

Files added

  • independent-publisher-connectors/Firmaradar/apiDefinition.swagger.json
  • independent-publisher-connectors/Firmaradar/apiProperties.json
  • independent-publisher-connectors/Firmaradar/README.md
  • independent-publisher-connectors/Firmaradar/icon.png
cert_searchCompanies cert_checkForetakIVanskeligheter cert_getCompanyProfile

Checklist

  • All connector files added to independent-publisher-connectors/Firmaradar/
  • paconn validate passes
  • Tested in own Power Platform tenant
  • README follows Independent Publisher template
  • Icon is 1024×1024 PNG on transparent background
  • CLA signed

@Tiwas Tiwas requested a review from a team as a code owner May 27, 2026 12:39
@Tiwas

Tiwas commented May 27, 2026

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree company="Firmaradar AS"

Bumps connector version from 0.3.0 to 0.3.1 and adds a setheader
policyTemplateInstance that sets X-FR-Client: power-automate on every
request.

X-FR-Client is the new Firmaradar Client identifier (renamed from
X-MCP-Client). Firmaradar backend recognizes both headers for at least
6 months; new connector installs will identify cleanly as Power
Automate.
@vmanoharas

Copy link
Copy Markdown
Contributor

Hi @Tiwas,

Thank you for your interest to submit Independent Publisher Connector.

Please refer below links.

Prepare connector package - https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

Independent Publisher Connector certification process - https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip

@Tiwas

Tiwas commented May 29, 2026

Copy link
Copy Markdown
Author

Hi @vmanoharas — thanks for picking this up! The submission follows both guides: independent-publisher-connectors/Firmaradar/ contains apiDefinition.swagger.json, apiProperties.json, README.md and a 1024×1024 icon.png, and the CLA is signed. The PR description already includes the paconn validate result (no errors) plus end-to-end test evidence with screenshots for getCompany, searchCompanies and checkForetakIVanskeligheter (all HTTP 200 in our tenant). Happy to make any adjustments the review needs — just let me know.

Removes the getSkattelister operation, its SkattelisterSelskap
definition, the Skattelister tag, and all README references to tax-list
lookups. The underlying capability was withdrawn for compliance reasons
(the tax-list data source is not available to the service), so the
connector no longer advertises or exposes it. Version bumped to 0.5.1
to align with the Firmaradar cross-platform baseline.

Pure removal — all other operations and their reviewed descriptions are
unchanged.
@vmanoharas

Copy link
Copy Markdown
Contributor

Hi @Tiwas,

Thank you for your response.

Please refer this link and prepare connector package and upload as part of the artifacts. https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission.

Please refer this PR for connector package zip file - https://github.com/microsoft/PowerPlatformConnectors/pull/4180/changes

Addresses the certification review request to provide a connector
package artifact (ref PR microsoft#4180).

- ConnectorPackage.zip: certification package (intro.md + Package
  Deployer package containing the connector solution and a
  proof-of-life flow solution). Verified with ConnectorPackageValidator.ps1.
- apiDefinition.swagger.json: drop the OAuth2 security definition; the
  connector authenticates via API key (X-API-Key header) only.
- apiProperties.json: set iconBrandColor to #da3b01 per independent
  publisher guidance.
- icon.png: opaque (non-transparent) background.
@Tiwas

Tiwas commented Jun 2, 2026

Copy link
Copy Markdown
Author

Hi @vmanoharas, thank you. I've added ConnectorPackage.zip under independent-publisher-connectors/Firmaradar/ as requested (same structure as PR #4180): intro.md plus the Package Deployer package containing the connector solution and a proof-of-life flow solution. I validated the structure with ConnectorPackageValidator.ps1 (validation successful).

I also made two small adjustments while preparing the package:

  • Switched the connector to API-key-only authentication (removed the unused OAuth2 security definition); it authenticates via the X-API-Key header.
  • Set iconBrandColor to #da3b01 per the independent-publisher guidance.

Please let me know if anything else is needed.

@vmanoharas

Copy link
Copy Markdown
Contributor

Hi @Tiwas,

Thank you for submitting the package, we have shared the MS form for Onevet verification, these details needed for onevet verification, please submit and notify us.

@Tiwas

Tiwas commented Jun 4, 2026

Copy link
Copy Markdown
Author

Could you re-share the verification form link here or confirm which email it was sent to? I haven't received it.

@vmanoharas

Copy link
Copy Markdown
Contributor

Hi @Tiwas,

We have shared again to the email mentioned in the package zip file - support@firmaradar.no

@Tiwas

Tiwas commented Jun 12, 2026

Copy link
Copy Markdown
Author

@vmanoharas Ok, I filled it out, but I don't really see the relevance. Also, Norway wasn't listed so I had to pick Sweden (neighboring country). Is there anything else I can do?

@vmanoharas

Copy link
Copy Markdown
Contributor

Hi @Tiwas,

Apologies for the inconvenience caused.

We have added Norway and resend the form, please fill the from. As during Onevet verification the details you provided should match with the govt issued proof.

@Tiwas

Tiwas commented Jun 12, 2026

Copy link
Copy Markdown
Author

@vmanoharas Thanks for the new form with the correct countries. I've now resubmitted.

@Tiwas

Tiwas commented Jun 12, 2026

Copy link
Copy Markdown
Author

I omitted my middle name as I don't ever use it. Do you want me to resubmit with that? Everything else should be identical to my ID and my registered home (and business) address. The email is my company email and not my github email.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants