Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

ruby-experian

Package Overview
Dependencies
Maintainers
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

ruby-experian

  • 0.1.3
  • Rubygems
  • Socket score

Version published
Maintainers
1
Created
Source

Ruby Experian

Tests

Use the Experian Axesor Informe 360 API with Ruby! 🩵

Allows you to get a detailed credit risk report for Spanish companies.

Bundler

Add this line to your application's Gemfile:

gem "ruby-experian"

And then execute:

$ bundle install

Gem install

Or install with:

$ gem install ruby-experian

and require with:

require "experian"

Usage

  • Get your user_code and password from https://axesor.es

Quickstart

For a quick test you can pass your user code and password directly to a new client:

client = Experian::Client.new(user_code: "user code goes here", password: "password goes here")

With Config

For a more robust setup, you can configure the gem with your API keys, for example in an experian.rb initializer file. Never hardcode secrets into your codebase - instead use something like dotenv to pass the keys safely into your environments.

Experian.configure do |config|
    config.user_code = ENV.fetch("EXPERIAN_USER_CODE")
    config.password = ENV.fetch("EXPERIAN_PASSWORD")
end

By default, this gem will look for the environment variables EXPERIAN_USER_CODE and EXPERIAN_PASSWORD to set the default values for user code and password.

Then you can create a client like this:

client = Experian::Client.new

You can still override the config defaults when making new clients; any options not included will fall back to any global config set with Experian.configure. e.g. in this example the base_uri, request_timeout, etc. will fallback to any set globally using Experian.configure, with only the password overridden:

client = Experian::Client.new(password: "some other password")
Custom timeout or base URI

The default timeout for any request using this library is 120 seconds. You can change that by passing a number of seconds to the request_timeout when initializing the client. You can also change the base URI used for all requests, eg. to use observability tools like Helicone.

client = Experian::Client.new(
    user_code: "user code goes here",
    base_uri: "https://oai.hconeai.com/",
    request_timeout: 240,
    extra_headers: {
      "Helicone-Auth": "Bearer HELICONE_API_KEY"
      "helicone-stream-force-format" => "true",
    }
)

or when configuring the gem:

Experian.configure do |config|
    config.user_code = ENV.fetch("EXPERIAN_USER_CODE")
    config.password = ENV.fetch("EXPERIAN_PASSWORD")
    config.base_uri = "https://oai.hconeai.com/" # Optional
    config.request_timeout = 240 # Optional
    config.extra_headers = {
      "Helicone-Auth": "Bearer HELICONE_API_KEY"
    } # Optional
end
Extra Headers per Client

You can dynamically pass headers per client object, which will be merged with any headers set globally with Experian.configure:

client = Experian::Client.new(user_code: "code goes here", password: "password goes here")
client.add_headers("X-Proxy-TTL" => "43200")
Verbose Logging

You can further configure the faraday connection by passing in a block to the client (e.g. to enable verbose logging with Ruby's Logger):

  client = Experian::Client.new do |f|
    f.response :logger, Logger.new($stdout), bodies: true
  end

Credit Report

You can hit the credit report api to get the 360 credit report from Experian by passing in a CIF to the call. Note that only some sections of the report are exposed. Other sections will be exposed as needed / requested.

The exposed sections for now are:

  • id
  • address
  • rating
  • number_of_employees
  • cnae
  • constitution_date
report = client.credit_report(cif: "cif goes here")
report.rating.inspect
# => "#<OpenStruct score=8, default_probability=0.529, risk=\"Mínimo\", size=\"Grande\">"

Trade Report

You can hit the trade report api to get the 360 trade report from Experian by passing in a CIF to the call. Note that only some sections of the report are exposed. Other sections will be exposed as needed / requested.

The exposed sections for now are:

  • model_200(period:)
  • address
  • rating
  • most_recent_number_of_employees
  • cnae
  • constitution_date
report = client.trade_report(cif: "cif goes here")
report.rating.inspect
# => "#<OpenStruct score=8, default_probability=0.529, risk=\"Mínimo\", size=\"Grande\">"

Development

After checking out the repo, run bin/setup to install dependencies. You can run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install.

Warning

If you have an EXPERIAN_USER_CODE and EXPERIAN_PASSWORD in your ENV, running the specs will use this to run the specs against the actual API, which will be slow! Remove it from your environment with unset or similar if you just want to run the specs against the stored VCR responses.

Release

In order to release this gem, you'll need the gem-release gem globally installed:

gem install gem-release

Second, run the specs without VCR so they actually hit the API. Set EXPERIAN_USER_CODE and EXPERIAN_PASSWORD in your environment or pass it in like this:

EXPERIAN_USER_CODE=code EXPERIAN_PASSWORD=password bundle exec rspec

Then update the version number in version.rb, update CHANGELOG.md, run bundle install to update Gemfile.lock, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/moraki-finance/ruby-experian. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the Ruby Experian project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.

FAQs

Package last updated on 16 Jun 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc